Mats Kindahl 124e830125 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. mysql-test/extra/binlog_tests/implicit.test: New test file to check implicit commits both inside and outside transactions. mysql-test/suite/binlog/t/binlog_implicit_commit.test: Test for implicit commit of SET AUTOCOMMIT and LOCK/UNLOCK TABLES. sql/set_var.cc: Adding code to commit pending transaction before changing option flags.		2009-09-23 13:20:48 +02:00
..
binlog.test	Fix for bug#45998: database crashes when running	2009-07-14 20:07:29 +05:00
binlog_insert_delayed.test
binlog_truncate.test	Bug #36763	2009-02-06 17:06:41 +01:00
blackhole.test
ctype_cp932.test
ctype_cp932_binlog.test
ctype_ucs_binlog.test
database.test
drop_temp_table.test
implicit.test	Bug #37221: SET AUTOCOMMIT=1 does not commit binary log	2009-09-23 13:20:48 +02:00
innodb_stat.test
insert_select-binlog.test
mix_innodb_myisam_binlog.test
mix_innodb_myisam_side_effects.test