8 Commits

Author	SHA1	Message	Date
monty@narttu.mysql.fi	7a54334443	Merge with 4.0.13	2003-06-05 17:33:38 +03:00
guilhem@mysql.com	3b974039f7	-- 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
vva@eagle.mysql.r18.ru	09348e271a	fixed 'STARTING BY' in replication	2003-05-21 14:54:02 -04:00
vva@eagle.mysql.r18.ru	ec247fd6af	changed processing of LOAD DATA in mysqlbinlog	2003-05-20 17:03:18 -04:00
monty@narttu.mysql.fi	a7708c7904	Merge with 4.0	2003-04-03 21:19:12 +03:00
vva@eagle.mysql.r18.ru	f45be5e6cd	added test for replication load data into temporary table with additional options	2003-04-03 12:54:08 -04:00
monty@mashka.mysql.fi	8acc22296c	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
monty@mashka.mysql.fi	8dd439e751	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