• unknown's avatar
    Bug #30244: row_count/found_rows does not replicate well · 385ef618
    unknown authored
     The functions ROW_COUNT/FOUND_ROWS are indeed not safe to be used in 
     statement based replication.
     Added code to declare them as such and switch the statement they're in
     to row based logging for mixed mode.
    
    
    sql/item_create.cc:
      Bug #30244: row_count/found_rows does not replicate well
       - add the functions to the set of "unsafe functions" 
         for statement based replication
    mysql-test/suite/rpl/r/rpl_row_unsafe_funcs.result:
      BitKeeper file /home/kgeorge/mysql/work/B30244-5.1-opt/mysql-test/suite/rpl/r/rpl_row_unsafe_funcs.result
    mysql-test/suite/rpl/t/rpl_row_unsafe_funcs.test:
      BitKeeper file /home/kgeorge/mysql/work/B30244-5.1-opt/mysql-test/suite/rpl/t/rpl_row_unsafe_funcs.test
    385ef618
rpl_row_unsafe_funcs.result 475 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;
CREATE TABLE t1 (a INT);
CREATE TABLE t2 (a INT, b INT);
INSERT INTO t1 SELECT 1;
INSERT INTO t1 VALUES (2),(3),(4),(5),(6);
INSERT INTO t2 SELECT 1, ROW_COUNT();
INSERT INTO t1 VALUES (2),(3),(4);
INSERT INTO t2 SELECT 2, ROW_COUNT();
SELECT b FROM t2 ORDER BY a;
b
1
3
SELECT b FROM t2 ORDER BY a;
b
1
3
DROP TABLE t1, t2;