summaryrefslogtreecommitdiff
path: root/strings/ChangeLog
diff options
context:
space:
mode:
authorMats Kindahl <mats@sun.com>2009-09-23 13:20:48 +0200
committerMats Kindahl <mats@sun.com>2009-09-23 13:20:48 +0200
commit8f35f7c907992c77b1bda584956cf8acf97e88d5 (patch)
tree05f9e5a91777fffa20de0e533bfef022ed954374 /strings/ChangeLog
parent5661e72623e66d9170dbe3e7913ff4f36b79100d (diff)
downloadmariadb-git-8f35f7c907992c77b1bda584956cf8acf97e88d5.tar.gz
Bug #37221: SET AUTOCOMMIT=1 does not commit binary log
When setting AUTOCOMMIT=1 after starting a transaction, the binary log did not commit the outstanding transaction. The reason was that the binary log commit function saw the values of the new settings, deciding that there were nothing to commit. Fixed the problem by moving the implicit commit to before the thread option flags were changed, so that the binary log sees the old values of the flags instead of the values they will take after the statement.
Diffstat (limited to 'strings/ChangeLog')
0 files changed, 0 insertions, 0 deletions