Bug #87983 mysql.exe 5.7.19 doesn't work with Workbench Data Import
Submitted: 4 Oct 2017 23:27 Modified: 15 Oct 2017 2:31
Reporter: Guest User Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.9 build 10690321 OS:Windows (10)
Assigned to: CPU Architecture:Any

[4 Oct 2017 23:27] Guest User
It is impossible to use the latest version of mysql.exe in Workbench to import data.

How to repeat:
In Workbench, go to Edit>Preferences>Administration and set "Path to mysql Tool" to the non-bundled version. Probably this: "C:\Program Files\MySQL\MySQL Server 5.7\bin\mysql.exe"

Import a MySQL dump using Data Import/Restore and the import will hang.

stop the import, blank out the "Path to mysql Tool" setting, try the import again, and it will work.

Suggested fix:
Fix the problem introduced by mysql.exe 5.7.19.

My own investigation revealed that when mysql.exe is started, the process is not started correctly. As in, the path after the ">" character in the command line is missing. If you look at the command line in Task Manager while importing, you will see the different arguments between the bundled and latest mysql.exe.
[5 Oct 2017 11:07] Chiranjeevi Battula
Hello John,

Thank you for the bug report.

[15 Oct 2017 2:31] Guest User
Sure thing. Any updates?