mirror of
https://github.com/MariaDB/server.git
synced 2025-07-03 01:48:12 +02:00
0680e31737
A deadlock forces the on going transaction to rollback implicitly. Within a transaction block, started with START TRANSACTION / BEGIN, implicit rollback doesn't reset OPTION_BEGIN flag. It results in a new implicit transaction to start when the next statement is executed. This behaviour is unexpected and should be fixed. However, we should note that there is no issue with rollback. We fix the issue to keep the behaviour of implicit rollback (deadlock) similar to explicit COMMIT and ROLLBACK i.e. the next statement after deadlock error is not going to start a transaction block implicitly unless autocommit is set to zero. |
||
|---|---|---|
| .. | ||
| include | ||
| r | ||
| t | ||