mariadb/mysql-test/r/rpl_relayrotate.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;
stop slave;
create table t1 (a int) engine=innodb;
reset slave;
start slave;
stop slave;
start slave;
select max(a) from t1;
max(a)
8000
drop table t1;
Replication: new code to not modify in-memory log positions until the COMMIT is executed, even if the transaction spans on >=2 relay logs (bug #53). New variable relay_log_purge =0\|1 New test to verify bug #53 2003-04-24 15:29:25 +02:00			`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;`
			`stop slave;`
WorkLog#1323 Deprecate the use of TYPE=... Preferred syntax is ENGINE= 2003-12-10 04:31:42 +00:00			`create table t1 (a int) engine=innodb;`
Replication: new code to not modify in-memory log positions until the COMMIT is executed, even if the transaction spans on >=2 relay logs (bug #53). New variable relay_log_purge =0\|1 New test to verify bug #53 2003-04-24 15:29:25 +02:00			`reset slave;`
			`start slave;`
			`stop slave;`
			`start slave;`
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			`select max(a) from t1;`
			`max(a)`
Replication: new code to not modify in-memory log positions until the COMMIT is executed, even if the transaction spans on >=2 relay logs (bug #53). New variable relay_log_purge =0\|1 New test to verify bug #53 2003-04-24 15:29:25 +02:00			`8000`
Cleaning DROP TABLE which is important if the tests are run in a certain order. This is because rpl_relayrotate.test uses InnoDB. Example of a failing sequence: rpl_relayrotate.test repl_user_variables.test rpl_relayrotate.test Explaination in the files. Btw all other tests which use InnoDB (innodb*.test) already have this final DROP TABLE. Removed a wrong comment of mine. 2003-05-22 22:29:44 +02:00			`drop table t1;`