unknown 508527a94c Bug #46998 mysqlbinlog can't output BEGIN even if the database is included in a transaction ... 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. client/mysqlbinlog.cc: Skip the database check for BEGIN/COMMIT/ROLLBACK log events. mysql-test/r/mysqlbinlog.result: Test result for bug#46998 mysql-test/suite/binlog/t/binlog_row_mysqlbinlog_db_filter.test: The test case is updated duo to the patch of bug#46998 mysql-test/t/mysqlbinlog.test: Added test to verify if the 'BEGIN', 'COMMIT' and 'ROLLBACK' are output in regardless of database filtering		2009-09-30 10:31:25 +08:00
..
r	auto-merge	2009-09-29 06:08:18 -07:00
std_data	Merge dl145h.mysql.com:/data0/mkindahl/mysql-5.1	2008-02-07 12:38:13 +01:00
t	Bug #46998 mysqlbinlog can't output BEGIN even if the database is included in a transaction	2009-09-30 10:31:25 +08:00
combinations	WL#4350 Options in my.cnf style config file should not start with --	2008-09-05 15:31:09 +02:00