mariadb/mysql-test/suite/binlog/t/binlog_database.test

# A wrapper to test that dropping a database is binlogged
# correctly. We test all three modes in the same file to avoid
# unecessary server restarts.

--source include/have_innodb.inc
--source include/have_binlog_format_statement.inc

set binlog_format=statement;
source extra/binlog_tests/database.test;
set binlog_format=mixed;
source extra/binlog_tests/database.test;
set binlog_format=row;
source extra/binlog_tests/database.test;

show databases;
Bug#32435: DROP DATABASE statement writes changes to mysql.proc table under RBR When replicating a DROP DATABASE statement with a database holding stored procedures, the changes to the mysql.proc table was recorded in the binary log under row-based replication. With this patch, the thread uses statement-logging format for the duration of the DROP DATABASE statement. The logging format is (already) reset at the end of the statement, so no additional code for resetting the logging format is necessary. sql/sql_db.cc: Clearing the row-based statement flag for the DROP DATABASE statement since it should always be replicated as a statement. mysql-test/extra/binlog_tests/database.test: New BitKeeper file ``mysql-test/extra/binlog_tests/database.test'' mysql-test/suite/binlog/r/binlog_database.result: New BitKeeper file ``mysql-test/suite/binlog/r/binlog_database.result'' mysql-test/suite/binlog/t/binlog_database.test: New BitKeeper file ``mysql-test/suite/binlog/t/binlog_database.test'' 2007-11-16 15:55:22 +01:00			`# A wrapper to test that dropping a database is binlogged`
			`# correctly. We test all three modes in the same file to avoid`
			`# unecessary server restarts.`

post-merge fixes. most tests pass. 5.3 merge is next 2011-07-02 22:12:12 +02:00			`--source include/have_innodb.inc`
			`--source include/have_binlog_format_statement.inc`

Bug#32435: DROP DATABASE statement writes changes to mysql.proc table under RBR When replicating a DROP DATABASE statement with a database holding stored procedures, the changes to the mysql.proc table was recorded in the binary log under row-based replication. With this patch, the thread uses statement-logging format for the duration of the DROP DATABASE statement. The logging format is (already) reset at the end of the statement, so no additional code for resetting the logging format is necessary. sql/sql_db.cc: Clearing the row-based statement flag for the DROP DATABASE statement since it should always be replicated as a statement. mysql-test/extra/binlog_tests/database.test: New BitKeeper file ``mysql-test/extra/binlog_tests/database.test'' mysql-test/suite/binlog/r/binlog_database.result: New BitKeeper file ``mysql-test/suite/binlog/r/binlog_database.result'' mysql-test/suite/binlog/t/binlog_database.test: New BitKeeper file ``mysql-test/suite/binlog/t/binlog_database.test'' 2007-11-16 15:55:22 +01:00			`set binlog_format=statement;`
			`source extra/binlog_tests/database.test;`
			`set binlog_format=mixed;`
			`source extra/binlog_tests/database.test;`
			`set binlog_format=row;`
			`source extra/binlog_tests/database.test;`

			`show databases;`