Bug #46998 mysqlbinlog can't output BEGIN even if the database is included in a transaction

Browse Source

The 'BEGIN/COMMIT/ROLLBACK' log event could be filtered out if the
database is not selected by --database option of mysqlbinlog command.
This can result in problem if there are some statements in the
transaction are not filtered out.

To fix the problem, mysqlbinlog will output 'BEGIN/ROLLBACK/COMMIT' 
in regardless of the database filtering rules.

...

This commit is contained in:

2009-09-30 10:31:25 +08:00

parent 00e5cea84d 869c011218

commit f4b6aeaf5b

5 changed files with 169 additions and 10 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

BIN

mysql-test/std_data/binlog_transaction.000001 Normal file

Binary file not shown.