mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
4dbcac20b4
The test case added in previous patch missed a RESET MASTER on test start up. Without it, showing binary log contents can sometimes show spurious entries from previously executed tests, ultimately causing test failure - result mismatch. The test file was added in: revid:luis.soares@sun.com-20100224190153-k0bpdx9abe88uoo2 This patch also moves the test case into binlog_innodb_row.test file. This way we avoid having yet another test file, binlog_row_innodb_truncate.test, whose only purpose is to host one test case. This had been actually suggested during original patch review, but somehow the binlog_innodb_row was missed when searching for a file to host the test case.
79 lines
2.2 KiB
Text
79 lines
2.2 KiB
Text
#
|
|
# Tests of innodb/binlog with the row binlog format
|
|
#
|
|
source include/have_innodb.inc;
|
|
source include/have_log_bin.inc;
|
|
source include/have_binlog_format_row.inc;
|
|
|
|
#
|
|
# Bug #40221 Replication failure on RBR + UPDATE the primary key
|
|
#
|
|
|
|
CREATE TABLE t1 (i int unique) ENGINE=innodb;
|
|
reset master;
|
|
|
|
# part 1: update can cause the dup key
|
|
|
|
begin;
|
|
insert into t1 values (1),(2);
|
|
--echo *** the following UPDATE query wont generate any updates for the binlog ***
|
|
--error ER_DUP_ENTRY
|
|
update t1 set i = 3 where i < 3;
|
|
commit;
|
|
|
|
--echo *** Results of the test: the binlog must have only Write_rows events not any Update_rows ***
|
|
source include/show_binlog_events.inc;
|
|
|
|
# part 2: insert can cause the dup key
|
|
|
|
delete from t1;
|
|
reset master;
|
|
|
|
begin;
|
|
insert into t1 values (1),(2);
|
|
--echo *** the following UPDATE query wont generate any updates for the binlog ***
|
|
--error ER_DUP_ENTRY
|
|
insert into t1 values (3),(4),(1),(2);
|
|
commit;
|
|
|
|
--echo *** Results of the test: the binlog must have only one Write_rows event not two ***
|
|
source include/show_binlog_events.inc;
|
|
|
|
drop table t1;
|
|
|
|
#
|
|
# BUG#51251
|
|
#
|
|
# The test case checks if truncating a temporary table created with
|
|
# engine InnoDB will not cause the truncate statement to be binlogged.
|
|
|
|
# Before patch for BUG#51251, the TRUNCATE statements below would be
|
|
# binlogged, which would cause the slave to fail with "table does not
|
|
# exist".
|
|
|
|
RESET MASTER;
|
|
|
|
CREATE TABLE t1 ( c1 int , primary key (c1)) ENGINE=InnoDB;
|
|
INSERT INTO t1 VALUES (1), (2), (3);
|
|
CREATE TEMPORARY TABLE IF NOT EXISTS t2 LIKE t1;
|
|
TRUNCATE TABLE t2;
|
|
DROP TABLE t1;
|
|
|
|
-- echo ###############################################
|
|
-- echo ### assertion: No event for 'TRUNCATE TABLE t2'
|
|
-- echo ###############################################
|
|
-- source include/show_binlog_events.inc
|
|
-- echo ###############################################
|
|
|
|
RESET MASTER;
|
|
|
|
CREATE TEMPORARY TABLE t1 (c1 int) Engine=InnoDB;
|
|
INSERT INTO t1 VALUES (1), (2), (3);
|
|
TRUNCATE t1;
|
|
DROP TEMPORARY TABLE t1;
|
|
|
|
-- echo ###############################################
|
|
-- echo ### assertion: No event for 'TRUNCATE TABLE t1'
|
|
-- echo ###############################################
|
|
-- source include/show_binlog_events.inc
|
|
-- echo ###############################################
|