mirror of
https://github.com/MariaDB/server.git
synced 2025-01-23 07:14:17 +01:00
aa7bf83a2f
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.
29 lines
1.1 KiB
Text
29 lines
1.1 KiB
Text
source include/have_log_bin.inc;
|
|
source include/have_innodb.inc;
|
|
|
|
# It is necessary to reset the master since otherwise the binlog test
|
|
# might show the wrong binary log. The default for SHOW BINLOG EVENTS
|
|
# is to show the first binary log, not the current one (which is
|
|
# actually a better idea).
|
|
|
|
RESET MASTER;
|
|
|
|
let $engine = InnoDB;
|
|
source extra/binlog_tests/binlog_truncate.test;
|
|
|
|
# Under transaction isolation level READ UNCOMMITTED and READ
|
|
# COMMITTED, InnoDB does not permit statement-based replication of
|
|
# row-deleting statement. In these cases, TRUNCATE TABLE should still
|
|
# be replicated as a statement.
|
|
|
|
let $before_truncate = SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
|
|
source extra/binlog_tests/binlog_truncate.test;
|
|
|
|
let $before_truncate = SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
|
|
source extra/binlog_tests/binlog_truncate.test;
|
|
|
|
let $before_truncate = SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
|
|
source extra/binlog_tests/binlog_truncate.test;
|
|
|
|
let $before_truncate = SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
|
|
source extra/binlog_tests/binlog_truncate.test;
|