mirror of
https://github.com/MariaDB/server.git
synced 2025-02-02 03:51:50 +01:00
94 lines
2.7 KiB
Text
94 lines
2.7 KiB
Text
# Test to test how logging is done depending on the capabilities of
|
|
# the engines. Unfortunately, we don't have a good row-only logging
|
|
# engine, and NDB does not really cut is since it is also
|
|
# self-logging. I'm using it nevertheless.
|
|
|
|
source include/have_blackhole.inc;
|
|
source include/have_ndb.inc;
|
|
source include/have_binlog_format_mixed_or_row.inc;
|
|
|
|
CREATE TABLE t1m (m INT, n INT) ENGINE=MYISAM;
|
|
CREATE TABLE t1b (b INT, c INT) ENGINE=BLACKHOLE;
|
|
CREATE TABLE t1n (e INT, f INT) ENGINE=NDB;
|
|
|
|
RESET MASTER;
|
|
|
|
SET SESSION BINLOG_FORMAT=STATEMENT;
|
|
|
|
INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2);
|
|
INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2);
|
|
|
|
UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c;
|
|
|
|
# I cannot use these statements since the rows logged to the NDB table
|
|
# eventually shows up in the binary log. I use them anyway, since once
|
|
# BUG#29222 is fixed, there will be a difference here.
|
|
echo *** Please look in binlog_multi_engine.test if you have a diff here ****;
|
|
START TRANSACTION;
|
|
INSERT INTO t1n VALUES (1,1), (1,2), (2,1), (2,2);
|
|
UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
|
|
UPDATE t1n, t1b SET e = 2, b = 3 WHERE f = c;
|
|
COMMIT;
|
|
|
|
TRUNCATE t1m;
|
|
TRUNCATE t1b;
|
|
TRUNCATE t1n;
|
|
|
|
source include/show_binlog_events.inc;
|
|
|
|
RESET MASTER;
|
|
|
|
SET SESSION BINLOG_FORMAT=MIXED;
|
|
|
|
INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2);
|
|
INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2);
|
|
INSERT INTO t1n VALUES (1,1), (1,2), (2,1), (2,2);
|
|
|
|
UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c;
|
|
error ER_BINLOG_LOGGING_IMPOSSIBLE;
|
|
UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
|
|
|
|
# Not possible to test this since NDB writes its own binlog, which
|
|
# might cause it to be out of sync with the results from MyISAM.
|
|
# This will generate an error once BUG#28722 is fixed.
|
|
|
|
#UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
|
|
|
|
error ER_BINLOG_LOGGING_IMPOSSIBLE;
|
|
UPDATE t1n, t1b SET e = 2, b = 3 WHERE f = c;
|
|
|
|
TRUNCATE t1m;
|
|
TRUNCATE t1b;
|
|
TRUNCATE t1n;
|
|
|
|
source include/show_binlog_events.inc;
|
|
|
|
RESET MASTER;
|
|
|
|
SET SESSION BINLOG_FORMAT=ROW;
|
|
|
|
INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2);
|
|
error ER_BINLOG_LOGGING_IMPOSSIBLE;
|
|
INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2);
|
|
INSERT INTO t1n VALUES (1,1), (1,2), (2,1), (2,2);
|
|
|
|
error ER_BINLOG_LOGGING_IMPOSSIBLE;
|
|
UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c;
|
|
error ER_BINLOG_LOGGING_IMPOSSIBLE;
|
|
UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
|
|
|
|
# Not possible to test this since NDB writes its own binlog, which
|
|
# might cause it to be out of sync with the results from MyISAM.
|
|
# This will generate an error once BUG#28722 is fixed.
|
|
|
|
#UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
|
|
|
|
error ER_BINLOG_LOGGING_IMPOSSIBLE;
|
|
UPDATE t1n, t1b SET e = 2, b = 3 WHERE f = c;
|
|
|
|
source include/show_binlog_events.inc;
|
|
|
|
RESET MASTER;
|
|
|
|
DROP TABLE t1m, t1b, t1n;
|
|
|