mariadb/mysql-test/suite/binlog/r/binlog_truncate_myisam.result

RESET MASTER;
CREATE TABLE t1 (a INT) ENGINE=MyISAM;
CREATE TABLE t2 (a INT) ENGINE=MyISAM;
INSERT INTO t2 VALUES (1),(2),(3);
**** Truncate of empty table shall be logged
TRUNCATE TABLE t1;
TRUNCATE TABLE t2;
show binlog events from <binlog_start>;
Log_name	Pos	Event_type	Server_id	End_log_pos	Info
master-bin.000001	#	Query	#	#	use `test`; TRUNCATE TABLE t1
master-bin.000001	#	Query	#	#	use `test`; TRUNCATE TABLE t2
DROP TABLE t1,t2;
Bug #36763 TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. Correcting some tests that was failing in pushbuild as well as fixing result file for some tests that are not executed in the default MTR run. 2009-02-10 22:26:37 +01:00			`RESET MASTER;`
Bug #36763 TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. There were two separate problems with the code, both of which are fixed with this patch: 1. An error was printed by InnoDB for TRUNCATE TABLE in statement mode when the in isolation levels READ COMMITTED and READ UNCOMMITTED since InnoDB does permit statement-based replication for DML statements. However, the TRUNCATE TABLE is not transactional, but is a DDL, and should therefore be allowed to be replicated as a statement. 2. The statement was not logged in mixed mode because of the error above, but the error was not reported to the client. This patch fixes the problem by treating TRUNCATE TABLE a DDL, that is, it is always logged as a statement and not reporting an error from InnoDB for TRUNCATE TABLE. 2009-02-06 17:06:41 +01:00			`CREATE TABLE t1 (a INT) ENGINE=MyISAM;`
			`CREATE TABLE t2 (a INT) ENGINE=MyISAM;`
			`INSERT INTO t2 VALUES (1),(2),(3);`
			`**** Truncate of empty table shall be logged`
			`TRUNCATE TABLE t1;`
			`TRUNCATE TABLE t2;`
			`show binlog events from <binlog_start>;`
			`Log_name Pos Event_type Server_id End_log_pos Info`
			master-bin.000001 # Query # # use `test`; TRUNCATE TABLE t1
			master-bin.000001 # Query # # use `test`; TRUNCATE TABLE t2
			`DROP TABLE t1,t2;`