--source include/master-slave.inc
--source include/have_binlog_format_mixed.inc

--connection slave
STOP SLAVE;
--source include/wait_for_slave_to_stop.inc

--enable_connect_log

--connection master
CREATE TABLE t1 (pk INT PRIMARY KEY) ENGINE=MyISAM;
INSERT INTO t1 VALUES (3),(2),(1);

--echo #-------------------------------------------------
--echo # Prepare a dump for initializing a slave
--echo # (run mysqldump --order-by-primary --master-data test)
--echo #-------------------------------------------------

--exec $MYSQL_DUMP --order-by-primary --master-data test > $MYSQLTEST_VARDIR/tmp/d.dump

--connection slave
--echo #-------------------------------------------------
--echo # Restore the dump on the slave
--echo #-------------------------------------------------

--exec $MYSQL_SLAVE test < $MYSQLTEST_VARDIR/tmp/d.dump

START SLAVE;
--disable_connect_log
--source include/wait_for_slave_to_start.inc
--enable_connect_log

--connection master

--echo #-------------------------------------------------
--echo # Since the rows can get updated in an arbitrary order
--echo # and stop in the middle due to the duplicate key error, 
--echo # the statement is actually unsafe, but is not recognized
--echo # as such and is logged in statement format
--echo #-------------------------------------------------

--error ER_DUP_ENTRY
UPDATE t1 SET pk = 5;
SHOW BINLOG EVENTS;

--echo #-------------------------------------------------
--echo # We have different data on master and slave
--echo #-------------------------------------------------

SELECT * FROM t1;
--sync_slave_with_master
SELECT * FROM t1;

--echo #----------------------------------
--echo # Now it's easy to break replication completely
--echo #----------------------------------

--connection master
DELETE FROM t1 LIMIT 3;
SHOW BINLOG EVENTS;

--sync_slave_with_master