Bug
Roll back failed due to implicit commit in truncate
Issue description
A new table format was created and there was an error in the meta system trigger 858, since it was only targeted towards computation and not columns. When it finally worked there were three column formats instead of one.
Developer comments
Revert the trigger to its faulty state and see what happened.
This only happens there is a successful save at the end. If there was n unsuccessful attempts before, there will be n+1 identical topics created.
This turned out to be wrong. It only surfaces then, since the label table is not updated after the rollback, the index does not show the topic, but it already exists.
This is a special case for this particular topic type and trigger. This system trigger uses a "truncate table" statement which causes an implicit commit.
A benchmark has shown that truncate is 10-15 times faster than delete on a table with 100.000 rows.
Rejection comment
Leave the truncate in for now. This error only takes effect when a change in the system topic map happens, which is very rare. The effects are also easily reverted by deleting the topics.
|
Work sessions2
Start |
2022-12-18T09:54:30
|
End |
2022-12-18T10:41:52
|
Participant |
Robert Cerny
|
Start |
2022-12-18T14:56:44
|
End |
2022-12-18T15:53:39
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.