mariadb/mysql-test/suite/versioning/t/rpl_mix.test
Sergei Golubchik 83ea839fb1 MDEV-15405 Mixed replication fails with "Could not execute Delete_rows_v1 event" upon DELETE HISTORY
Allow slave thread to set time for system versioning

Note that every binlog event stores now(0), while microseconds
are only stored when they're actually used in the query.

Meaning for unversioned->versioned replication, there will be
no microseconds. Need to compensate for that.
2018-02-25 14:31:15 +01:00

19 lines
537 B
Text

--source include/have_binlog_format_mixed.inc
--source include/master-slave.inc
#
# MDEV-15405 Mixed replication fails with "Could not execute Delete_rows_v1 event" upon DELETE HISTORY
#
CREATE TABLE t1 (pk INT PRIMARY KEY, i INT) WITH SYSTEM VERSIONING;
INSERT INTO t1 VALUES (1,10),(2,20);
UPDATE t1 SET i = 100;
# This is to imitiate any real-life situation which causes a switch to row format
SET BINLOG_FORMAT= ROW;
DELETE HISTORY FROM t1;
--sync_slave_with_master
connection master;
drop table t1;
--source include/rpl_end.inc