stk_test_assertions must be reloaded at every run
Bug #1149848 reported by
Federico Razzoli
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| STK-Unit | Status tracked in Trunk | |||||
| Trunk |
Fix Released
|
Medium
|
Federico Razzoli | |||
Bug Description
stk_test_assertions must be re-created everytime. If not, some obects miss from the DB. Thus, some assertions fail.
| tags: | added: test-stk-unit-assertions |
Revision history for this message
| Federico Razzoli (santec) wrote | #1 |
Revision history for this message
| Federico Razzoli (santec) wrote | #2 |
To post a comment you must log in.
The problem was that we had MEMORY tables and 1 trigger, which were needed to make some tests pass.
Triggers cannot be created whithin a Stored Routine, so we created everything at the moment of installation. But doing so, MEMORY tables die at server shutdown. And storage engines different from MEMORY are not fast enough for that test.
Now I create within before_all_tests everything I can create there. And at the installation time, I create a unused non-MEMORY table, with a trigger attached.
Dont change this anymore.