2
# Bug #797: If a query is ignored on slave (replicate-ignore-table) the slave
3
# still checks that it has the same error as on the master.
4
##########################################################################
5
# 2006-02-07 JBM Added error code 1022 for NDB Engine + ORDER BY
6
##########################################################################
8
-- source include/master-slave.inc
11
create table t1 (a int primary key);
12
create table t4 (a int primary key);
13
# generate an error that goes to the binlog
14
--error 1022, ER_DUP_ENTRY
15
insert into t1 values (1),(1);
16
insert into t4 values (1),(2);
19
# as the t1 table is ignored on the slave, the slave should be able to sync
21
# check that the table has been ignored, because otherwise the test is nonsense
22
show tables like 't1';
23
show tables like 't4';
24
SELECT * FROM test.t4 ORDER BY a;
31
# Now test that even critical errors (connection killed)
32
# are ignored if rules allow it.
33
# The "kill" idea was copied from rpl000001.test.
36
select get_lock('crash_lock%20C', 10);
39
create table t2 (a int primary key);
40
insert into t2 values(1);
41
create table t3 (id int);
42
insert into t3 values(connection_id());
43
send update t2 set a = a + 1 + get_lock('crash_lock%20C', 10);
46
let $wait_condition= SELECT a > 1 FROM t2;
47
source include/wait_condition.inc;
48
select (@id := id) - id from t3;
51
insert into t4 values (3),(4);
53
--error 0,1053,2013,1048
59
SELECT * FROM test.t4 ORDER BY a;
67
# Adding comment for force manual merge 5.0 -> wl1012. delete me if needed