mariadb/mysql-test/t/binlog_stm_drop_tmp_tbl.test

# This is a wrapper for binlog.test so that the same test case can be used 
# For both statement and row based bin logs 9/19/2005 [jbm]

-- source include/have_binlog_format_mixed_or_statement.inc
-- source extra/binlog_tests/drop_temp_table.test
WL#1012: All changes as one single changeset. This includes both code and test cases. 2005-12-22 06:39:02 +01:00			`# This is a wrapper for binlog.test so that the same test case can be used`
			`# For both statement and row based bin logs 9/19/2005 [jbm]`

Changes made according to HLD/LLD. The following is an excerption from the WL. 1. Change so that MIXED is default format 1.1 to change the default for command line --binlog-format 1.2 to alter global_system_variables.binlog_format calculation basing on command line --binlog-format parameter and its default. 2. Change test suite so that more testing is done by MIXED format. 2.1 to check if there are test cases requiring --binlog-foramt=statement via `source include/have_binlog_format_statement.inc' and affected by altering the latter to be "mixed". 2.2 to check the content of such vulnerable cases to find if extending to the mixed does not modify results. In that case simply substitute source arguments as explained. 2.3 if a test in mixed mode deals with features triggering row-binlogging then if necessary we can switch explicitly to statement mode or create another test to run with non-recommended STATEMENT mode Particullarily, extracting INSERT DELAYED binlogging subtest for statement mode is performed, and the snippet is moved into a separate test file. Note that since now all three modes verify this use case through 3 different tests. No changes in item 3 of HLD appeared to be needed. 2006-08-30 10:22:43 +03:00			`-- source include/have_binlog_format_mixed_or_statement.inc`
WL#1012: All changes as one single changeset. This includes both code and test cases. 2005-12-22 06:39:02 +01:00			`-- source extra/binlog_tests/drop_temp_table.test`