mariadb/mysql-test/suite/rpl/r/rpl_loaddata.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;
reset master;
select last_insert_id();
last_insert_id()
0
create table t1(a int not null auto_increment, b int, primary key(a) );
load data infile '../../std_data/rpl_loaddata.dat' into table t1;
select last_insert_id();
last_insert_id()
1
create temporary table t2 (day date,id int(9),category enum('a','b','c'),name varchar(60));
load data infile '../../std_data/rpl_loaddata2.dat' into table t2 fields terminated by ',' optionally enclosed by '%' escaped by '@' lines terminated by '\n##\n' starting by '>' ignore 1 lines;
create table t3 (day date,id int(9),category enum('a','b','c'),name varchar(60));
insert into t3 select * from t2;
select * from t1;
a	b
1	10
2	15
select * from t3;
day	id	category	name
2003-02-22	2461	b	a a a @ %  ' " a
2003-03-22	2161	c	asdf
2003-03-22	2416	a	bbbbb
drop table t1;
drop table t2;
drop table t3;
create table t1(a int, b int, unique(b));
insert into t1 values(1,10);
load data infile '../../std_data/rpl_loaddata.dat' into table t1;
set global sql_slave_skip_counter=1;
start slave;
show slave status;;
Slave_IO_State	#
Master_Host	127.0.0.1
Master_User	root
Master_Port	MASTER_PORT
Connect_Retry	1
Master_Log_File	master-bin.000001
Read_Master_Log_Pos	#
Relay_Log_File	#
Relay_Log_Pos	#
Relay_Master_Log_File	master-bin.000001
Slave_IO_Running	Yes
Slave_SQL_Running	Yes
Replicate_Do_DB	
Replicate_Ignore_DB	
Replicate_Do_Table	
Replicate_Ignore_Table	#
Replicate_Wild_Do_Table	
Replicate_Wild_Ignore_Table	
Last_Errno	0
Last_Error	
Skip_Counter	0
Exec_Master_Log_Pos	#
Relay_Log_Space	#
Until_Condition	None
Until_Log_File	
Until_Log_Pos	0
Master_SSL_Allowed	No
Master_SSL_CA_File	
Master_SSL_CA_Path	
Master_SSL_Cert	
Master_SSL_Cipher	
Master_SSL_Key	
Seconds_Behind_Master	#
Master_SSL_Verify_Server_Cert	No
Last_IO_Errno	0
Last_IO_Error	
Last_SQL_Errno	0
Last_SQL_Error	
Replicate_Ignore_Server_Ids	
Master_Server_Id	1
set sql_log_bin=0;
delete from t1;
set sql_log_bin=1;
load data infile '../../std_data/rpl_loaddata.dat' into table t1;
stop slave;
change master to master_user='test';
change master to master_user='root';
show slave status;;
Slave_IO_State	#
Master_Host	127.0.0.1
Master_User	root
Master_Port	MASTER_PORT
Connect_Retry	1
Master_Log_File	master-bin.000001
Read_Master_Log_Pos	#
Relay_Log_File	#
Relay_Log_Pos	#
Relay_Master_Log_File	master-bin.000001
Slave_IO_Running	No
Slave_SQL_Running	No
Replicate_Do_DB	
Replicate_Ignore_DB	
Replicate_Do_Table	
Replicate_Ignore_Table	#
Replicate_Wild_Do_Table	
Replicate_Wild_Ignore_Table	
Last_Errno	0
Last_Error	
Skip_Counter	0
Exec_Master_Log_Pos	#
Relay_Log_Space	#
Until_Condition	None
Until_Log_File	
Until_Log_Pos	0
Master_SSL_Allowed	No
Master_SSL_CA_File	
Master_SSL_CA_Path	
Master_SSL_Cert	
Master_SSL_Cipher	
Master_SSL_Key	
Seconds_Behind_Master	#
Master_SSL_Verify_Server_Cert	No
Last_IO_Errno	0
Last_IO_Error	
Last_SQL_Errno	0
Last_SQL_Error	
Replicate_Ignore_Server_Ids	
Master_Server_Id	1
set global sql_slave_skip_counter=1;
start slave;
set sql_log_bin=0;
delete from t1;
set sql_log_bin=1;
load data infile '../../std_data/rpl_loaddata.dat' into table t1;
stop slave;
reset slave;
show slave status;;
Slave_IO_State	#
Master_Host	127.0.0.1
Master_User	root
Master_Port	MASTER_PORT
Connect_Retry	1
Master_Log_File	
Read_Master_Log_Pos	4
Relay_Log_File	#
Relay_Log_Pos	#
Relay_Master_Log_File	
Slave_IO_Running	No
Slave_SQL_Running	No
Replicate_Do_DB	
Replicate_Ignore_DB	
Replicate_Do_Table	
Replicate_Ignore_Table	#
Replicate_Wild_Do_Table	
Replicate_Wild_Ignore_Table	
Last_Errno	0
Last_Error	
Skip_Counter	0
Exec_Master_Log_Pos	#
Relay_Log_Space	#
Until_Condition	None
Until_Log_File	
Until_Log_Pos	0
Master_SSL_Allowed	No
Master_SSL_CA_File	
Master_SSL_CA_Path	
Master_SSL_Cert	
Master_SSL_Cipher	
Master_SSL_Key	
Seconds_Behind_Master	#
Master_SSL_Verify_Server_Cert	No
Last_IO_Errno	0
Last_IO_Error	
Last_SQL_Errno	0
Last_SQL_Error	
Replicate_Ignore_Server_Ids	
Master_Server_Id	1
reset master;
create table t2 (day date,id int(9),category enum('a','b','c'),name varchar(60),
unique(day)) engine=MyISAM;
load data infile '../../std_data/rpl_loaddata2.dat' into table t2 fields
terminated by ',' optionally enclosed by '%' escaped by '@' lines terminated by
'\n##\n' starting by '>' ignore 1 lines;
ERROR 23000: Duplicate entry '2003-03-22' for key 'day'
select * from t2;
day	id	category	name
2003-02-22	2461	b	a a a @ %  ' " a
2003-03-22	2161	c	asdf
start slave;
select * from t2;
day	id	category	name
2003-02-22	2461	b	a a a @ %  ' " a
2003-03-22	2161	c	asdf
alter table t2 drop key day;
delete from t2;
load data infile '../../std_data/rpl_loaddata2.dat' into table t2 fields
terminated by ',' optionally enclosed by '%' escaped by '@' lines terminated by
'\n##\n' starting by '>' ignore 1 lines;
ERROR 23000: Duplicate entry '2003-03-22' for key 'day'
drop table t1, t2;
drop table t1, t2;
CREATE TABLE t1 (word CHAR(20) NOT NULL PRIMARY KEY) ENGINE=INNODB;
LOAD DATA INFILE "../../std_data/words.dat" INTO TABLE t1;
ERROR 23000: Duplicate entry 'Aarhus' for key 'PRIMARY'
DROP TABLE IF EXISTS t1;
-												Change client_flag to unsigned long (16 -> 32 bits) to handle more options.
Don't use new password format if mysql.user has old format
tables_priv was not reset on FLUSH PRIVILEGES if tables_priv was empty
Portability fixes for Windows

											
										
										
											2003-01-18 16:39:21 +02:00
+								stop slave;
-												Guard against compiling without -fno-exceptions
Allocate bigger default thread stack because of problems with glibc
Fixed bug in UPDATE ... not_null_field=expression_that_returns_null
Fixed bug in replication when using auto_increment and LOAD DATA INFILE

											
										
										
											2003-01-14 11:27:26 +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;
-												Change client_flag to unsigned long (16 -> 32 bits) to handle more options.
Don't use new password format if mysql.user has old format
tables_priv was not reset on FLUSH PRIVILEGES if tables_priv was empty
Portability fixes for Windows

											
										
										
											2003-01-18 16:39:21 +02:00
+								start 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
+								reset master;
-												WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements. 
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully 
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.

Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().

Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.

											
										
										
											2006-07-09 17:52:19 +02:00
+								select last_insert_id();
 								last_insert_id()
 
-												Guard against compiling without -fno-exceptions
Allocate bigger default thread stack because of problems with glibc
Fixed bug in UPDATE ... not_null_field=expression_that_returns_null
Fixed bug in replication when using auto_increment and LOAD DATA INFILE

											
										
										
											2003-01-14 11:27:26 +02:00
+								create table t1(a int not null auto_increment, b int, primary key(a) );
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								load data infile '../../std_data/rpl_loaddata.dat' into table t1;
-												WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements. 
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully 
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.

Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().

Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.

											
										
										
											2006-07-09 17:52:19 +02:00
+								select last_insert_id();
 								last_insert_id()
 
-												added test for replication load data into temporary table with additional options

											
										
										
											2003-04-03 12:54:08 -04:00
+								create temporary table t2 (day date,id int(9),category enum('a','b','c'),name varchar(60));
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								load data infile '../../std_data/rpl_loaddata2.dat' into table t2 fields terminated by ',' optionally enclosed by '%' escaped by '@' lines terminated by '\n##\n' starting by '>' ignore 1 lines;
-												added test for replication load data into temporary table with additional options

											
										
										
											2003-04-03 12:54:08 -04:00
+								create table t3 (day date,id int(9),category enum('a','b','c'),name varchar(60));
 								insert into t3 select * from t2;
-												Guard against compiling without -fno-exceptions
Allocate bigger default thread stack because of problems with glibc
Fixed bug in UPDATE ... not_null_field=expression_that_returns_null
Fixed bug in replication when using auto_increment and LOAD DATA INFILE

											
										
										
											2003-01-14 11:27:26 +02:00
+								select * from t1;
 								a	b
 	10
 	15
-												added test for replication load data into temporary table with additional options

											
										
										
											2003-04-03 12:54:08 -04:00
+								select * from t3;
 								day	id	category	name
 -02-22	2461	b	a a a @ %  ' " a
 -03-22	2161	c	asdf
-												Fix for BUG#1391:
"If LOAD DATA INFILE 'small_file' fails on master, slave leaves temp files"
(the bug is in the master)

											
										
										
											2003-09-25 00:14:46 +02:00
+-03-22	2416	a	bbbbb
-												Guard against compiling without -fno-exceptions
Allocate bigger default thread stack because of problems with glibc
Fixed bug in UPDATE ... not_null_field=expression_that_returns_null
Fixed bug in replication when using auto_increment and LOAD DATA INFILE

											
										
										
											2003-01-14 11:27:26 +02:00
+								drop table t1;
-												added test for replication load data into temporary table with additional options

											
										
										
											2003-04-03 12:54:08 -04:00
+								drop table t2;
 								drop table t3;
-												-- Waiting for Monty's approval before push --
Bug 571: play LOAD DATA INFILE the same way on the slave as it was on the master: 
if it was with IGNORE, do it with IGNORE,
if it was with REPLACE, do it with REPLACE,
and (the change) if it was with nothing, do it with nothing (not with IGNORE !!).
Bug 573: print a proper error message in case of duplicate entry in LOAD DATA INFILE
on the slave, i.e. a message where the keyname and key value appear :
'Duplicate entry '1' for key 1' and not 'Duplicate entry '%-.64s' for key %d'

											
										
										
											2003-06-03 15:47:29 +02:00
+								create table t1(a int, b int, unique(b));
 								insert into t1 values(1,10);
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								load data infile '../../std_data/rpl_loaddata.dat' into table t1;
-bugfixes:
- Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
for that.
- Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
SLAVE STATUS". Now these reset the errors.

											
										
										
											2003-08-04 10:59:44 +02:00
+								set global sql_slave_skip_counter=1;
 								start slave;
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								show slave status;;
 								Slave_IO_State	#
 								Master_Host	127.0.0.1
 								Master_User	root
 								Master_Port	MASTER_PORT
 								Connect_Retry	1
 								Master_Log_File	master-bin.000001
-												WL#2687 WL#5072 BUG#40278 BUG#47175

Non-transactional updates that take place inside a transaction present problems
for logging because they are visible to other clients before the transaction
is committed, and they are not rolled back even if the transaction is rolled
back. It is not always possible to log correctly in statement format when both
transactional and non-transactional tables are used in the same transaction.

In the current patch, we ensure that such scenario is completely safe under the
ROW and MIXED modes.
											
										
										
											2009-11-03 19:02:56 +00:00
+								Read_Master_Log_Pos	#
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								Relay_Log_File	#
 								Relay_Log_Pos	#
 								Relay_Master_Log_File	master-bin.000001
 								Slave_IO_Running	Yes
 								Slave_SQL_Running	Yes
 								Replicate_Do_DB
 								Replicate_Ignore_DB
 								Replicate_Do_Table
 								Replicate_Ignore_Table	#
 								Replicate_Wild_Do_Table
 								Replicate_Wild_Ignore_Table
 								Last_Errno	0
 								Last_Error
 								Skip_Counter	0
-												WL#2687 WL#5072 BUG#40278 BUG#47175

Non-transactional updates that take place inside a transaction present problems
for logging because they are visible to other clients before the transaction
is committed, and they are not rolled back even if the transaction is rolled
back. It is not always possible to log correctly in statement format when both
transactional and non-transactional tables are used in the same transaction.

In the current patch, we ensure that such scenario is completely safe under the
ROW and MIXED modes.
											
										
										
											2009-11-03 19:02:56 +00:00
+								Exec_Master_Log_Pos	#
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								Relay_Log_Space	#
 								Until_Condition	None
 								Until_Log_File
 								Until_Log_Pos	0
 								Master_SSL_Allowed	No
 								Master_SSL_CA_File
 								Master_SSL_CA_Path
 								Master_SSL_Cert
 								Master_SSL_Cipher
 								Master_SSL_Key
 								Seconds_Behind_Master	#
 								Master_SSL_Verify_Server_Cert	No
 								Last_IO_Errno	0
 								Last_IO_Error
 								Last_SQL_Errno	0
 								Last_SQL_Error
-												backporting bug@27808 fixes
											
										
										
											2009-10-01 19:44:53 +03:00
+								Replicate_Ignore_Server_Ids
 								Master_Server_Id	1
-bugfixes:
- Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
for that.
- Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
SLAVE STATUS". Now these reset the errors.

											
										
										
											2003-08-04 10:59:44 +02:00
+								set sql_log_bin=0;
 								delete from t1;
 								set sql_log_bin=1;
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								load data infile '../../std_data/rpl_loaddata.dat' into table t1;
-bugfixes:
- Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
for that.
- Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
SLAVE STATUS". Now these reset the errors.

											
										
										
											2003-08-04 10:59:44 +02:00
+								stop slave;
 								change master to master_user='test';
 								change master to master_user='root';
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								show slave status;;
 								Slave_IO_State	#
 								Master_Host	127.0.0.1
 								Master_User	root
 								Master_Port	MASTER_PORT
 								Connect_Retry	1
 								Master_Log_File	master-bin.000001
-												WL#2687 WL#5072 BUG#40278 BUG#47175

Non-transactional updates that take place inside a transaction present problems
for logging because they are visible to other clients before the transaction
is committed, and they are not rolled back even if the transaction is rolled
back. It is not always possible to log correctly in statement format when both
transactional and non-transactional tables are used in the same transaction.

In the current patch, we ensure that such scenario is completely safe under the
ROW and MIXED modes.
											
										
										
											2009-11-03 19:02:56 +00:00
+								Read_Master_Log_Pos	#
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								Relay_Log_File	#
 								Relay_Log_Pos	#
 								Relay_Master_Log_File	master-bin.000001
 								Slave_IO_Running	No
 								Slave_SQL_Running	No
 								Replicate_Do_DB
 								Replicate_Ignore_DB
 								Replicate_Do_Table
 								Replicate_Ignore_Table	#
 								Replicate_Wild_Do_Table
 								Replicate_Wild_Ignore_Table
 								Last_Errno	0
 								Last_Error
 								Skip_Counter	0
-												WL#2687 WL#5072 BUG#40278 BUG#47175

Non-transactional updates that take place inside a transaction present problems
for logging because they are visible to other clients before the transaction
is committed, and they are not rolled back even if the transaction is rolled
back. It is not always possible to log correctly in statement format when both
transactional and non-transactional tables are used in the same transaction.

In the current patch, we ensure that such scenario is completely safe under the
ROW and MIXED modes.
											
										
										
											2009-11-03 19:02:56 +00:00
+								Exec_Master_Log_Pos	#
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								Relay_Log_Space	#
 								Until_Condition	None
 								Until_Log_File
 								Until_Log_Pos	0
 								Master_SSL_Allowed	No
 								Master_SSL_CA_File
 								Master_SSL_CA_Path
 								Master_SSL_Cert
 								Master_SSL_Cipher
 								Master_SSL_Key
 								Seconds_Behind_Master	#
 								Master_SSL_Verify_Server_Cert	No
 								Last_IO_Errno	0
 								Last_IO_Error
 								Last_SQL_Errno	0
 								Last_SQL_Error
-												backporting bug@27808 fixes
											
										
										
											2009-10-01 19:44:53 +03:00
+								Replicate_Ignore_Server_Ids
 								Master_Server_Id	1
-bugfixes:
- Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
for that.
- Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
SLAVE STATUS". Now these reset the errors.

											
										
										
											2003-08-04 10:59:44 +02:00
+								set global sql_slave_skip_counter=1;
 								start slave;
 								set sql_log_bin=0;
 								delete from t1;
 								set sql_log_bin=1;
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								load data infile '../../std_data/rpl_loaddata.dat' into table t1;
-bugfixes:
- Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
for that.
- Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
SLAVE STATUS". Now these reset the errors.

											
										
										
											2003-08-04 10:59:44 +02:00
+								stop slave;
 								reset slave;
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								show slave status;;
 								Slave_IO_State	#
 								Master_Host	127.0.0.1
 								Master_User	root
 								Master_Port	MASTER_PORT
 								Connect_Retry	1
 								Master_Log_File
 								Read_Master_Log_Pos	4
 								Relay_Log_File	#
 								Relay_Log_Pos	#
 								Relay_Master_Log_File
 								Slave_IO_Running	No
 								Slave_SQL_Running	No
 								Replicate_Do_DB
 								Replicate_Ignore_DB
 								Replicate_Do_Table
 								Replicate_Ignore_Table	#
 								Replicate_Wild_Do_Table
 								Replicate_Wild_Ignore_Table
 								Last_Errno	0
 								Last_Error
 								Skip_Counter	0
-												WL#2687 WL#5072 BUG#40278 BUG#47175

Non-transactional updates that take place inside a transaction present problems
for logging because they are visible to other clients before the transaction
is committed, and they are not rolled back even if the transaction is rolled
back. It is not always possible to log correctly in statement format when both
transactional and non-transactional tables are used in the same transaction.

In the current patch, we ensure that such scenario is completely safe under the
ROW and MIXED modes.
											
										
										
											2009-11-03 19:02:56 +00:00
+								Exec_Master_Log_Pos	#
-												WL#342 heartbeat

backporting from 6.0 code base to 5.1.

											
										
										
											2009-09-29 14:16:23 +03:00
+								Relay_Log_Space	#
 								Until_Condition	None
 								Until_Log_File
 								Until_Log_Pos	0
 								Master_SSL_Allowed	No
 								Master_SSL_CA_File
 								Master_SSL_CA_Path
 								Master_SSL_Cert
 								Master_SSL_Cipher
 								Master_SSL_Key
 								Seconds_Behind_Master	#
 								Master_SSL_Verify_Server_Cert	No
 								Last_IO_Errno	0
 								Last_IO_Error
 								Last_SQL_Errno	0
 								Last_SQL_Error
-												backporting bug@27808 fixes
											
										
										
											2009-10-01 19:44:53 +03:00
+								Replicate_Ignore_Server_Ids
 								Master_Server_Id	1
-												Fix for BUG#1391:
"If LOAD DATA INFILE 'small_file' fails on master, slave leaves temp files"
(the bug is in the master)

											
										
										
											2003-09-25 00:14:46 +02:00
+								reset master;
 								create table t2 (day date,id int(9),category enum('a','b','c'),name varchar(60),
-												WWe now store the catalog in Query_log_event in binlog WITHOUT its end zero.
This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4
are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had
been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just
before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE.
If slave fails in Execute_load_query_log_event::exec_event(),
don't delete the file (so that it's re-usable at next START SLAVE).
And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not
executed at all on the slave" (storing an Execute_load_query_log_event
to binlog, with its error code, instead of Delete_file_log_event).

											
										
										
											2005-03-25 14:51:17 +01:00
+								unique(day)) engine=MyISAM;
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								load data infile '../../std_data/rpl_loaddata2.dat' into table t2 fields
-												Fix for BUG#1391:
"If LOAD DATA INFILE 'small_file' fails on master, slave leaves temp files"
(the bug is in the master)

											
										
										
											2003-09-25 00:14:46 +02:00
+								terminated by ',' optionally enclosed by '%' escaped by '@' lines terminated by
 								'\n##\n' starting by '>' ignore 1 lines;
-												WL#1563 - Modify MySQL to support fast CREATE/DROP INDEX
Change "duplicate key" message to print key name
instead of key number.

											
										
										
											2006-01-23 12:17:05 +01:00
+								ERROR 23000: Duplicate entry '2003-03-22' for key 'day'
-												WWe now store the catalog in Query_log_event in binlog WITHOUT its end zero.
This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4
are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had
been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just
before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE.
If slave fails in Execute_load_query_log_event::exec_event(),
don't delete the file (so that it's re-usable at next START SLAVE).
And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not
executed at all on the slave" (storing an Execute_load_query_log_event
to binlog, with its error code, instead of Delete_file_log_event).

											
										
										
											2005-03-25 14:51:17 +01:00
+								select * from t2;
 								day	id	category	name
 -02-22	2461	b	a a a @ %  ' " a
 -03-22	2161	c	asdf
 								start slave;
 								select * from t2;
 								day	id	category	name
 -02-22	2461	b	a a a @ %  ' " a
 -03-22	2161	c	asdf
 								alter table t2 drop key day;
 								delete from t2;
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								load data infile '../../std_data/rpl_loaddata2.dat' into table t2 fields
-												WWe now store the catalog in Query_log_event in binlog WITHOUT its end zero.
This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4
are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had
been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just
before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE.
If slave fails in Execute_load_query_log_event::exec_event(),
don't delete the file (so that it's re-usable at next START SLAVE).
And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not
executed at all on the slave" (storing an Execute_load_query_log_event
to binlog, with its error code, instead of Delete_file_log_event).

											
										
										
											2005-03-25 14:51:17 +01:00
+								terminated by ',' optionally enclosed by '%' escaped by '@' lines terminated by
 								'\n##\n' starting by '>' ignore 1 lines;
-												WL#1563 - Modify MySQL to support fast CREATE/DROP INDEX
Change "duplicate key" message to print key name
instead of key number.

											
										
										
											2006-01-23 12:17:05 +01:00
+								ERROR 23000: Duplicate entry '2003-03-22' for key 'day'
-												BUG#38350: Many tests don't clean up after themselves on exit.
Problem: Many test cases don't clean up after themselves (fail
to drop tables or fail to reset variables). This implies that:
(1) check-testcase in the new mtr that currently lives in
5.1-rpl failed. (2) it may cause unexpected results in
subsequent tests.
Fix: make all tests clean up.
Also: cleaned away unnecessary output in rpl_packet.result
Also: fixed bug where rpl_log called RESET MASTER with a running
slave. This is not supposed to work.
Also: removed unnecessary code from rpl_stm_EE_err2 and made it
verify that an error occurred.
Also: removed unnecessary code from rpl_ndb_ctype_ucs2_def.

											
										
										
											2008-11-13 20:19:00 +01:00
+								drop table t1, t2;
 								drop table t1, t2;
-												BUG#17233 : LOAD DATA INFILE: failure causes mysqld dbug_assert, binlog not flushed 

This patch corrects a bug involving a LOAD DATA INFILE operation on a 
transactional table. It corrects a problem in the error handler by moving
the transactional table check and autocommit_or_rollback operation to the 
end of the error handler. 

The problem was an assert was thrown after the operation completed. The 
assert found a non-sunk event in the transaction cache. The events in the 
transaction cache were added after commit_or_rollack and thereafter nothing 
removed them.

An additional test case was added to detect this
condition.

											
										
										
											2007-05-08 10:17:00 -04:00
+								CREATE TABLE t1 (word CHAR(20) NOT NULL PRIMARY KEY) ENGINE=INNODB;
-												WL#4189
 - dynamic configuration support
 - safe process
 - cleanups
 - create new suite for fedarated

											
										
										
											2007-12-12 18:19:24 +01:00
+								LOAD DATA INFILE "../../std_data/words.dat" INTO TABLE t1;
-												BUG#17233 : LOAD DATA INFILE: failure causes mysqld dbug_assert, binlog not flushed 

This patch corrects a bug involving a LOAD DATA INFILE operation on a 
transactional table. It corrects a problem in the error handler by moving
the transactional table check and autocommit_or_rollback operation to the 
end of the error handler. 

The problem was an assert was thrown after the operation completed. The 
assert found a non-sunk event in the transaction cache. The events in the 
transaction cache were added after commit_or_rollack and thereafter nothing 
removed them.

An additional test case was added to detect this
condition.

											
										
										
											2007-05-08 10:17:00 -04:00
+								ERROR 23000: Duplicate entry 'Aarhus' for key 'PRIMARY'
 								DROP TABLE IF EXISTS t1;