Bug #573 slave prints an incomplete error message when LOAD DATA INFILE gives dup entry
Submitted: 3 Jun 2003 6:45 Modified: 3 Jul 2003 5:36
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[3 Jun 2003 6:45] Guilhem Bichot
Before bug 571 is fixed, the only way to get a duplicate entry error on the slave
with LOAD DATA INFILE is : see how-to-repeat. Then the slave prints on the .err file :
030603 15:17:01  Slave: Error 'Duplicate entry '%-.64s' for key %d' running load data infile, error_code=1062
whereas it should substitute like this for example:
030603 15:33:32  Slave: Error 'Duplicate entry '1' for key 1' running load data infile, error_code=1062

How to repeat:
create table t(a int auto_increment primary key);
insert into t values(1);
start slave;
load data infile 'file' replace into table t;

where 'file' contains 1.
(to reproduce the bug one must have the auto_inc column and the REPLACE keyword).
[3 Jul 2003 5:36] Michael Widenius
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at 

Will be fixed in 4.0.14