| Current Path : /usr/opt/mysql57/mysql-test/suite/binlog/r/ |
FreeBSD hs32.drive.ne.jp 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Wed Jan 14 12:18:08 JST 2015 root@hs32.drive.ne.jp:/sys/amd64/compile/hs32 amd64 |
| Current File : //usr/opt/mysql57/mysql-test/suite/binlog/r/binlog_stm_do_db.result |
SET @old_isolation_level= @@session.tx_isolation; Warnings: Warning 1287 '@@tx_isolation' is deprecated and will be removed in a future release. Please use '@@transaction_isolation' instead SET @@session.tx_isolation= 'READ-COMMITTED'; Warnings: Warning 1287 '@@tx_isolation' is deprecated and will be removed in a future release. Please use '@@transaction_isolation' instead CREATE DATABASE b42829; use b42829; CREATE TABLE t1 (x int, y int) engine=InnoDB; CREATE TABLE t2 (x int, y int) engine=InnoDB; CREATE DATABASE b42829_filtered; use b42829_filtered; CREATE TABLE t1 (x int, y int) engine=InnoDB; CREATE TABLE t2 (x int, y int) engine=InnoDB; SET @@session.sql_log_bin= 0; INSERT INTO b42829_filtered.t1 VALUES (100,100); INSERT INTO b42829.t1 VALUES (100,100); SET @@session.sql_log_bin= 1; ### assertion: the inserts will not raise log error because ### binlog-do-db is filtering used database INSERT INTO t2 VALUES (1,2), (1,3), (1,4); INSERT INTO t1 SELECT * FROM t2; ### assertion: assert that despite updating a not filtered ### database this wont trigger an error as the ### used database is the filtered one. UPDATE b42829_filtered.t1 ft1, b42829.t1 nft1 SET ft1.x=1, nft1.x=2; use b42829; ### assertion: the statements *will* raise log error because ### binlog-do-db is not filtering used database BEGIN; INSERT INTO t2 VALUES (1,2), (1,3), (1,4); ERROR HY000: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. UPDATE b42829_filtered.t1 ft1, b42829.t1 nft1 SET ft1.x=1, nft1.x=2; ERROR HY000: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. INSERT INTO t1 SELECT * FROM t2; ERROR HY000: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. COMMIT; ### assertion: filtered events did not make into the binlog include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info master-bin.000001 # Query # # CREATE DATABASE b42829 master-bin.000001 # Query # # use `b42829`; CREATE TABLE t1 (x int, y int) engine=InnoDB master-bin.000001 # Query # # use `b42829`; CREATE TABLE t2 (x int, y int) engine=InnoDB DROP DATABASE b42829; DROP DATABASE b42829_filtered; SET @@session.tx_isolation= @old_isolation_level; Warnings: Warning 1287 '@@tx_isolation' is deprecated and will be removed in a future release. Please use '@@transaction_isolation' instead