• hezx@hezx.(none)'s avatar
    Bug#30998 Drop View breaks replication if view does not exist · c267a923
    hezx@hezx.(none) authored
      
    When executing drop view statement on the master, the statement is written
    into bin-log without checking for possible errors, so the statement would 
    always be bin-logged with error code cleared even if some error might occur, 
    for example, some of the views being dropped does not exist. This would cause 
    failure on the slave.
    
    Writing bin-log after check for errors, if at least one view has been dropped
    the query is bin-logged possible with an error.
    c267a923
rpl_drop_view.result 816 Bytes
stop slave;
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
reset master;
reset slave;
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
start slave;
drop table if exists t1, t2;
drop view if exists v1, v2, v3, not_exist_view;
create table t1 (a int);
create table t2 (b int);
create table t3 (c int);
create view v1 as select * from t1;
create view v2 as select * from t2;
create view v3 as select * from t3;
drop view not_exist_view;
ERROR 42S02: Unknown table 'not_exist_view'
drop view v1, not_exist_view;
ERROR 42S02: Unknown table 'not_exist_view'
select * from v1;
ERROR 42S02: Table 'test.v1' doesn't exist
drop view v2, v3;
select * from v1;
ERROR 42S02: Table 'test.v1' doesn't exist
select * from v2;
ERROR 42S02: Table 'test.v2' doesn't exist
select * from v3;
ERROR 42S02: Table 'test.v3' doesn't exist