Bug
Incorrect handling of deadlocks
Issue description
When a deadlock happens, Topincs repeats the query, but does not rerun all the queries up to the deadlock. These were rollback implicitly by MySQL. This causes the user to have the false impression that the data was saved, when in fact it is not. Thankfully this happens only twice a year, but surfaced in a database with lots of writing request during a certain period of the day. Additionally there has to be one hot topic (in this case the next day). The deadlock occurs when trying to update the modification timestamp of the hot topic.
|
Work sessions3
Start |
2019-11-22T14:04:32
|
End |
2019-11-22T15:45:23
|
Participant |
Robert Cerny
|
Start |
2019-11-23T08:28:26
|
End |
2019-11-23T08:58:36
|
Participant |
Robert Cerny
|
Start |
2019-11-25T07:55:07
|
End |
2019-11-25T10:26:48
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.