File: rpl_mix.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (19 lines) | stat: -rw-r--r-- 532 bytes parent folder | download | duplicates (4) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
 
--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 rpl_common.inc