Debian Codegraph @

mysql-test/suite/binlog/r/binlog_variables_log_statements_unsafe_for_binlog.result

raw
1 # restart
2 CALL mtr.add_suppression("Unsafe statement written to the binary log");
3 CREATE TABLE test.unsafe (i int auto_increment primary key, j int) engine = innodb;
4 INSERT INTO test.unsafe (j) VALUES (1), (2), (3);
5 SCENARIO 1
6 SET GLOBAL log_statements_unsafe_for_binlog= ON;
7 Warnings:
8 Warning 1287 '@@log_statements_unsafe_for_binlog' is deprecated and will be removed in a future release.
9 UPDATE test.unsafe SET j = 4 LIMIT 1;
10 Warnings:
11 Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.
12 include/assert_grep.inc [Exactly one row should be written to the error log.]
13 SCENARIO 2
14 SET GLOBAL log_statements_unsafe_for_binlog= OFF;
15 Warnings:
16 Warning 1287 '@@log_statements_unsafe_for_binlog' is deprecated and will be removed in a future release.
17 UPDATE test.unsafe SET j = 4 LIMIT 1;
18 Warnings:
19 Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.
20 DROP TABLE test.unsafe;
21 SET GLOBAL log_statements_unsafe_for_binlog= 1;
22 Warnings:
23 Warning 1287 '@@log_statements_unsafe_for_binlog' is deprecated and will be removed in a future release.