1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
# It's true only in statement-based replication that a statement which
# updates no rows (UPDATE/DELETE) is binlogged; in row-based
# replication, as we log modified rows, nothing is binlogged in this
# case. So this test is meaningul only in statement-based (and if it was
# enabled in row-based, it would fail as expected).
-- source include/have_binlog_format_mixed_or_statement.inc
source include/master-slave.inc;
# see if DROP DATABASE is binlogged even if no effect
connection slave;
create database mysqltest;
connection master;
drop database if exists mysqltest;
--source include/sync_slave_sql_with_master.inc
# can't read dir
--replace_result "Errcode: 1" "Errcode: X" "Errcode: 2" "Errcode: X" \\ /
--error 1049
show tables from mysqltest;
# see if DROP TABLE is binlogged even if no effect
connection slave;
create table t1 (a int);
connection master;
drop table if exists t1;
--source include/sync_slave_sql_with_master.inc
# table does not exist
--error 1146
select * from t1;
# see if single-table DELETE is binlogged even if no effect
connection master;
create table t1 (a int, b int);
--source include/sync_slave_sql_with_master.inc
insert into t1 values(1,1);
connection master;
delete from t1;
--source include/sync_slave_sql_with_master.inc
select * from t1;
# see if single-table UPDATE is binlogged even if no effect
insert into t1 values(1,1);
connection master;
insert into t1 values(2,1);
update t1 set a=2;
--source include/sync_slave_sql_with_master.inc
select * from t1;
# End of 4.1 tests
# see if multi-table UPDATE is binlogged even if no effect (BUG#13348)
connection master;
create table t2 (a int, b int);
delete from t1;
insert into t1 values(1,1);
insert into t2 values(1,1);
--source include/sync_slave_sql_with_master.inc
# force a difference to see if master's multi-UPDATE will correct it
update t1 set a=2;
connection master;
UPDATE t1, t2 SET t1.a = t2.a;
--source include/sync_slave_sql_with_master.inc
select * from t1;
select * from t2;
# See if multi-table DELETE is binlogged even if no effect
connection master;
delete from t1;
delete from t2;
--source include/sync_slave_sql_with_master.inc
# force a difference to see if master's multi-DELETE will correct it
insert into t1 values(1,1);
insert into t2 values(1,1);
connection master;
DELETE t1.*, t2.* from t1, t2;
--source include/sync_slave_sql_with_master.inc
select * from t1;
select * from t2;
# cleanup
connection master;
drop table t1, t2;
--source include/sync_slave_sql_with_master.inc
--source include/rpl_end.inc
|
