MySQL Bugs: #87983: mysql.exe 5.7.19 doesn't work with Workbench Data Import

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:	Won't Fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.3.9 build 10690321	OS:	Windows (10)
Assigned to:		CPU Architecture:	Any

Description:
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.

Hello John,

Thank you for the bug report.

Thanks,
Chiranjeevi.

Sure thing. Any updates?

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.