Bug #51583 Executing load data local infile cause the workbench to crash
Submitted: 28 Feb 2010 3:48 Modified: 14 Apr 2010 8:20
Reporter: Chuck Stoner Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.16 Beta OS:Mac OS X
Assigned to: CPU Architecture:Any

[28 Feb 2010 3:48] Chuck Stoner
Description:
The following commands resulted in the workbench crashing. I tried the 5 truncate commands and that worked fine. It apparently is the first of the load data commands that actually causes the crash. I then used MySQL Query Browser and pasted each of the commands in turn and they were executed without issue.

If you like, I can provide the load files as well as the table sqls.

truncate products_options;
truncate products_options_values;
truncate products_attributes;
truncate products_attributes_download;
truncate products_options_values_to_products_options;

load data local infile 'three dog/website/oscom_site_build/products_options.txt' into table products_options columns terminated by '|';
load data local infile 'three dog/website/oscom_site_build/products_options_values.txt' into table products_options_values columns terminated by '|';
load data local infile 'three dog/website/oscom_site_build/products_attributes.txt' into table products_attributes columns terminated by '|';

How to repeat:
trye to execute the 3 load data commands
[28 Feb 2010 9:04] Valeriy Kravchuk
Please, provide CREATE TABLE statements and data to load to repeat the crash.
[28 Feb 2010 12:55] Chuck Stoner
Table create, delimited data, and SQL command file

Attachment: osCom_Site_build.zip (application/zip, text), 4.30 KiB.

[28 Feb 2010 12:57] Chuck Stoner
Table create, delimited data files, and SQL command file attached.
[1 Mar 2010 16:22] Valeriy Kravchuk
Verified just as described with your scripts and data.
[1 Mar 2010 16:23] Valeriy Kravchuk
Crash information collected by the OS

Attachment: crash.txt (text/plain), 44.64 KiB.

[14 Apr 2010 8:20] Sergei Tkachenko
Duplicates the bug #49694.