MySQL Bugs: #95481: Workbench import wizard extremely, agonizingly, painfully slow

Bug #95481	Workbench import wizard extremely, agonizingly, painfully slow
Submitted:	22 May 2019 22:05	Modified:	4 Apr 2021 12:19
Reporter:	John Fowler	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.16	OS:	Any (all)
Assigned to:		CPU Architecture:	Any (all)

Description:
The "Table Data Import Wizard" option in the latest MySQL Workbench is not usable, due to its speed.  After my most recent data import, MySQL Workbench proudly reported the following:

    File XXX.csv was imported in 105.372 s
    Table XXX has been used
    66 records imported

66 Records in 105 seconds!  That's a new slow record!

There was a defect #80140 opened for a prior version, but it seemed to be ignored. There are plenty of people commenting on this issue and providing solutions (use Load Data Infile) on Stack Overflow.  Just google "mysql workbench table data import slow" to see much discussion concerning this issue.

I can't imagine what could possibly make the import take more than 1 second per record unless you are closing and re-opening the database connection for every single row.

For your own pride in producing a quality DB client, please investigate and fix this.  As it is, the option is unusable for a large number of rows.

How to repeat:
Create a table, any table any number of columns.  Import a CSV of data using the import wizard.  Get yourself a cup of coffee while it imports.  This will take a while...

Suggested fix:
Give it some of the caffeine from your coffee, and perhaps a little crack cocaine as well.  Whatever makes it work faster.

Thank you for the bug report. Please provide (private if you wish) the create table statement, the cvs file and description of your hardware and OS so we could compare what you are reporting. 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".

Why was this closed? 

Sheez, there is no need of providing "the create table statement, the cvs file and description of your hardware and OS"!

Create ANY csv with (say) three random columns of text of  length about 15 chars, about 5000 records.
Import into a (preferably remote, with some network latency) mysql server (I'm using 5.6).

It's ridiculously slow, impossible to work. 

Please fix this.

Using Mysql Workbench 8.0.19 (64 bits community) on Windows 10.

This is never going to be fixed, is it? If you're unwilling to do the work make data import useable, just remove the feature.

I'm experiencing this issue as well, in Workbench 8.0 CE on Windows 10. As noted in another comment, there is nothing special about the db/table to reproduce this. I have a simple table with three varchar columns (email, first name, last name). Importing from csv takes a couple seconds per record (!!!). The software really should NOT be creating a new statement for each row.

As a workaround (not solution - Oracle, please fix this), you can use LOAD DATA LOCAL INFILE. To enable this in Workbench, add "OPT_LOCAL_INFILE=1" to your db connection settings (Connection -> Advanced -> Others). With that set, reconnect to your db and then run the following command (example based on Windows filesystem)("IGNORE 1 LINES" if you have a header row in your file).

LOAD DATA LOCAL INFILE 'C:\\Path\\to\\your\\file.csv' INTO TABLE table_name
FIELDS TERMINATED BY ',' LINES TERMINATED BY '\r\n' IGNORE 1 LINES;

Duplicate of https://bugs.mysql.com/bug.php?id=101803.

this is indeed ridiculous for such a commonly required use case- I can use the import wizard in toad to load a file to a table (with no FKs btw) in less than  1 second. Table import wizard in mysql workbench is taking minutes on the same table and then I just kill it through frustration.