MySQL Bugs: #21503: LOAD DATA INFILE - duplicated rows in table

Bug #21503	LOAD DATA INFILE - duplicated rows in table
Submitted:	8 Aug 2006 13:03	Modified:	30 Sep 2006 11:47
Reporter:	Marko Pecar	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	5.0.24	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any
Tags:	duplicates, LOAD DATA INFILE

Description:
When using a script with MySQL Query Browser to fill a database of 26 tables from text files using CHAR(36) type and containing UUID values, after all LOAD DATA INFILE commands are complete, some tables contain duplicate or even triplicate of all rows. 

There is no problem if CHAR(36) is changed to INT and text files are created accordingly.

The text files are generated so that no options are required in LOAD DATA statements (tab separated fields, LF terminated rows). 

At the time of import there are no indexes on the tables. 

The problem does not occour if LOAD DATA INFILE commands are executed in a "Resultset" window one by one.

How to repeat:
1. Create a database and tables
2. Use a script with multiple LOAD DATA INFILE statements (e.g. "LOAD DATA INFILE 'd:\\mysql\\club_history.tbl' INTO TABLE CLUB_HISTORY;")

Thank you for a problem report. Looks like a QB-related problem. Please, specify what exact version of Query Browser is used. Complete test case, with CREATE TABLE statements and text files to load, is also welocmed.

I am sorry but I will not have access to the files for more than a month now...

1. I agree that the problem is QB related. I use the latest distribution of GUI tools (at least at the time of bug submission).

2. I found out that the problem occurs if I execute a script of "LOAD DATA..." statements but not if I execute the same script in a query window one statement at the time. 

3. It is critical that you use the tables with NO indexes defined!

Regards,
Marko

I was unable to repeat with table/scripts on my own, could you please
provide the table definition/scripts and then re-open this bug when
done. Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".