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

# File for specialities regarding replication from or to InnoDB
# tables.

source include/have_innodb.inc;
source include/have_binlog_format_mixed_or_statement.inc;
source include/master-slave.inc;

source extra/rpl_tests/rpl_innodb.test;
--source include/rpl_end.inc
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 20:02:56 +01:00			`# File for specialities regarding replication from or to InnoDB`
			`# tables.`

			`source include/have_innodb.inc;`
BUG#53452 Inconsistent behavior of binlog_direct_non_transactional_updates with temp table This patch introduces two key changes in the replication's behavior. Firstly, it reverts part of BUG#51894 which puts any update to temporary tables into the trx-cache. Now, updates to temporary tables are handled according to the type of their engines as a regular table. Secondly, an unsafe mixed statement, (i.e. a statement that access transactional table as well non-transactional or temporary table, and writes to any of them), are written into the trx-cache in order to minimize errors in the execution when the statement logging format is in use. Such changes has a direct impact on which statements are classified as unsafe statements and thus part of BUG#53259 is reverted. 2010-08-20 04:59:58 +02:00			`source include/have_binlog_format_mixed_or_statement.inc;`
remove few obscure, unused, or misused mtr features 2012-02-06 18:42:18 +01:00			`source include/master-slave.inc;`
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 20:02:56 +01:00
			`source extra/rpl_tests/rpl_innodb.test;`
Merged BUG#49978 from 5.1-bugteam to 5.5-bugteam. 2010-12-19 18:15:12 +01:00			`--source include/rpl_end.inc`