mariadb/mysql-test/r/rpl_loaddata_rule_m.result

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 database if exists mysqltest;
stop slave;
create database mysqltest;
create table t1(a int, b int, unique(b));
use mysqltest;
load data infile '../../std_data/rpl_loaddata.dat' into table test.t1;
show binlog events from 95;
Log_name	Pos	Event_type	Server_id	End_log_pos	Info
drop database mysqltest;
After merge fixes. Note that mix_innodb_myisam_binlog and union fails after this patch (Will be fixed shortly by maintaners of this code) 2003-09-11 18:06:23 +02:00			`stop slave;`
First commit for fixing BUG#1100 "LOAD DATA INFILE is badly filtered by binlog--db rules". There will probably be a second final one to merge Dmitri's changes to rpl_log.result and mine. 2 new tests: rpl_loaddata_rule_m : test of logging of LOAD DATA INFILE when the master has binlog--db rules, rpl_loaddata_rule_s : test of logging of LOAD DATA INFILE when the slave has binlog-*-db rules and --log-slave-updates. 2003-08-20 23:24:45 +02:00			`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;`
After merge fixes. Note that mix_innodb_myisam_binlog and union fails after this patch (Will be fixed shortly by maintaners of this code) 2003-09-11 18:06:23 +02:00			`start slave;`
Fixes after merge 2003-10-08 11:01:58 +02:00			`drop database if exists mysqltest;`
Replication: Now the I/O thread (in flush_master_info()) flushes the relay log to disk after reading every event. Slower but provides additionnal safety in case of brutal crash. I had to make the flush optional (i.e. add a if(some_bool_argument) in the function) because sometimes flush_master_info() is called when there is no usable relay log (the relay log's IO_CACHE is not initialized so can't be flushed). 2003-11-23 17:02:59 +01:00			`stop slave;`
Fixes after merge 2003-10-08 11:01:58 +02:00			`create database mysqltest;`
First commit for fixing BUG#1100 "LOAD DATA INFILE is badly filtered by binlog--db rules". There will probably be a second final one to merge Dmitri's changes to rpl_log.result and mine. 2 new tests: rpl_loaddata_rule_m : test of logging of LOAD DATA INFILE when the master has binlog--db rules, rpl_loaddata_rule_s : test of logging of LOAD DATA INFILE when the slave has binlog-*-db rules and --log-slave-updates. 2003-08-20 23:24:45 +02:00			`create table t1(a int, b int, unique(b));`
Fixes after merge 2003-10-08 11:01:58 +02:00			`use mysqltest;`
First commit for fixing BUG#1100 "LOAD DATA INFILE is badly filtered by binlog--db rules". There will probably be a second final one to merge Dmitri's changes to rpl_log.result and mine. 2 new tests: rpl_loaddata_rule_m : test of logging of LOAD DATA INFILE when the master has binlog--db rules, rpl_loaddata_rule_s : test of logging of LOAD DATA INFILE when the slave has binlog-*-db rules and --log-slave-updates. 2003-08-20 23:24:45 +02:00			`load data infile '../../std_data/rpl_loaddata.dat' into table test.t1;`
This is the final commit for Worklog tasks: * A more dynamic binlog format which allows small changes (1064) * Log session variables in Query_log_event (1063) It contains a few bugfixes (which I made when running the testsuite). I carefully updated the results of the testsuite (i.e. I checked for every one, if the difference between .reject and .result could be explained). Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently, so I could neither run the few tests which require --manager, nor check that they pass nor modify their .result. But for builds, we don't run with --manager. Apart from --manager, the full testsuite passes, with Valgrind too (no errors). I'm going to push in the next minutes. Remains: update the manual. Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone; this is normal at it makes assumptions on thread ids. I will fix this one day in 4.1. 2003-12-19 22:40:23 +01:00			`show binlog events from 95;`
			`Log_name Pos Event_type Server_id End_log_pos Info`
Fixes after merge 2003-10-08 11:01:58 +02:00			`drop database mysqltest;`