mariadb/mysql-test/suite/rpl/t/rpl_mixed_mixing_engines.test

###################################################################################
# This test cases evaluates the mixture of non-transactional and transcational
# tables. For further details, please, read WL#2687 and WL#5072.
###################################################################################
--source include/have_binlog_format_mixed.inc
--source include/master-slave.inc
--source include/have_innodb.inc

let $engine_type=Innodb;
--source extra/rpl_tests/rpl_mixing_engines.test
WL#2687 WL#5072 BUG#40278 BUG#47175 Non-transactional updates that take place inside a transaction present problems for logging because they are visible to other clients before the transaction is committed, and they are not rolled back even if the transaction is rolled back. It is not always possible to log correctly in statement format when both transactional and non-transactional tables are used in the same transaction. In the current patch, we ensure that such scenario is completely safe under the ROW and MIXED modes. 2009-11-03 19:02:56 +00:00			`###################################################################################`
			`# This test cases evaluates the mixture of non-transactional and transcational`
			`# tables. For further details, please, read WL#2687 and WL#5072.`
			`###################################################################################`
			`--source include/have_binlog_format_mixed.inc`
			`--source include/master-slave.inc`
			`--source include/have_innodb.inc`

			`let $engine_type=Innodb;`
			`--source extra/rpl_tests/rpl_mixing_engines.test`