mariadb/mysql-test/std_data
unknown de04eb6c37 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/t/mysqlbinlog.test:
  Added test to verify if the 'BEGIN', 'COMMIT' and 'ROLLBACK' are output
  in regardless of database filtering
2009-09-30 10:01:52 +08:00
..
funcs_1 Fix for 2008-03-31 19:48:02 +02:00
ndb_backup50_data_be BUG#29674 Restore/backup are endian compatible in 5.0 2007-08-07 18:07:57 +00:00
ndb_backup50_data_le BUG#29674 Restore/backup are endian compatible in 5.0 2007-08-07 18:07:57 +00:00
14897.frm A fix for Bug#14897 "ResultSet.getString("table.column") sometimes 2006-08-30 00:38:58 +04:00
bad_gis_data.dat bug #22372 2006-12-06 21:47:29 +04:00
binlog_transaction.000001 Bug #46998 mysqlbinlog can't output BEGIN even if the database is included in a transaction 2009-09-30 10:01:52 +08:00
bug15328.cnf Bug#15328 Segmentation fault occured if my.cnf is invalid for escape sequence 2006-05-11 14:13:14 +02:00
bug16266.000001 Fix for BUG#16266: Definer is not fully qualified error during replication. 2006-03-01 14:13:07 +03:00
bug19371.frm Bug#19371 VARBINARY() have trailing zeros after upgrade from 4.1 2006-11-09 12:00:27 +01:00
bug19371.MYD Bug#19371 VARBINARY() have trailing zeros after upgrade from 4.1 2006-11-09 12:00:27 +01:00
bug19371.MYI Bug#19371 VARBINARY() have trailing zeros after upgrade from 4.1 2006-11-09 12:00:27 +01:00
bug30435_5k.txt bug#30435 2007-12-23 11:18:46 +02:00
bug30435_10k_items.txt bug#30435 2007-12-23 11:18:46 +02:00
bug35469.dat Fix tree: 2008-03-28 23:39:47 +03:00
bug36055.frm Fixed bug #36055: mysql_upgrade doesn't really 'upgrade' tables 2008-05-12 21:01:13 +05:00
bug36055.MYD Fixed bug #36055: mysql_upgrade doesn't really 'upgrade' tables 2008-05-12 21:01:13 +05:00
bug36055.MYI Fixed bug #36055: mysql_upgrade doesn't really 'upgrade' tables 2008-05-12 21:01:13 +05:00
cacert.pem Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT" 2009-01-28 16:18:50 +02:00
client-cert.pem Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT" 2009-01-28 16:18:50 +02:00
client-key.pem Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT" 2009-01-28 16:18:50 +02:00
corrupt-relay-bin.000624 BUG#31793 (log event corruption causes crash): 2007-11-09 13:43:09 +01:00
des_key_file Added FLUSH DES_KEY_FILE. 2001-12-13 15:53:18 +02:00
Index.xml Bug#28916 LDML doesn't work for utf8 2007-06-07 17:55:55 +05:00
init_file.dat Bug#23240 --init_file statements with NOW() reports '1970-01-01 11:00:00'as the date time 2007-02-19 14:57:54 +01:00
loaddata1.dat Fixed that reading a DATE string of 000000 is interpreted as 0000-00-00 instead of 2000-00-00 2003-05-05 14:52:39 +03:00
loaddata2.dat Move test that uses many tables (in query_cache.test) to separate test so that we can get it 'skipped' instead of 'failed' on system where we can't open many files. 2003-08-22 04:07:40 +03:00
loaddata3.dat Extend max_allowed_packet to 2G in mysql and mysqldump (Bug #2105) 2003-12-14 06:39:52 +02:00
loaddata4.dat Extend max_allowed_packet to 2G in mysql and mysqldump (Bug #2105) 2003-12-14 06:39:52 +02:00
loaddata5.dat Fix LOAD DATA to handle having the escape and enclosed-by character 2005-06-22 16:14:14 -07:00
loaddata6.dat Bug#15126 character_set_database is not replicated (LOAD DATA INFILE need it) 2007-02-28 17:06:57 +04:00
loaddata_dq.dat Merge mysql.com:/home/jimw/my/mysql-4.1-clean 2005-10-26 14:11:08 -07:00
loaddata_pair.dat Bug#11401: Setting thd->lex so that engines (i.e., InnoDB) recognizes 2005-07-05 13:55:54 +02:00
loaddata_utf8.dat BUG#45516 SQL thread does not use database charset properly 2009-08-12 11:54:05 +08:00
master-bin.000001 Changed binlog name padding from binlog.001 to binlog.000001 2002-10-29 15:11:13 -07:00
Moscow_leap Bug #39920: MySQL cannot deal with Leap Second expression in string literal. 2008-12-01 16:18:35 +02:00
ndb_config_mycnf1.cnf ndb 2005-09-30 12:19:15 +02:00
ndb_config_mycnf2.cnf Bug #13009 No gaps allowed in node id number sequence 2005-10-12 14:17:39 +02:00
rpl_loaddata.dat Guard against compiling without -fno-exceptions 2003-01-14 11:27:26 +02:00
rpl_loaddata2.dat Fix for BUG#1391: 2003-09-25 00:14:46 +02:00
rpl_timezone.dat testing repl of timezone with LOAD DATA INFILE (hourra!) 2005-03-24 16:43:50 +01:00
server-cert.pem Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT" 2009-01-28 16:18:50 +02:00
server-key.pem Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT" 2009-01-28 16:18:50 +02:00
server8k-cert.pem Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT" 2009-01-28 16:18:50 +02:00
server8k-key.pem Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT" 2009-01-28 16:18:50 +02:00
trunc_binlog.000001 fix rpl_trunc_binlog to test the new behaviour 2005-02-19 22:24:13 +01:00
untrusted-cacert.pem Add an untrusted cacert used when testing 2006-05-03 14:10:22 +02:00
vchar.frm Update results for new varchar handling 2004-12-07 15:47:00 +02:00
warnings_loaddata.dat update the test for LOAD DATA INFILE warnings 2003-04-22 00:54:33 -07:00
words.dat Fixed multi-table-delete for InnoDB tables 2003-02-17 02:14:37 +02:00