MySQL Bugs: #59737: Dump-Imports fails when WorkBench is placed in folder with spaces in its name

Bug #59737	Dump-Imports fails when WorkBench is placed in folder with spaces in its name
Submitted:	26 Jan 2011 11:24	Modified:	25 May 2011 1:57
Reporter:	Christian Fruth	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.31	OS:	MacOS (10.5, 10.6)
Assigned to:	Maksym Yehorov	CPU Architecture:	Any

Description:
It is not possible to import a dump when MySQLWorkbench.app is placed in a folder with spaces. The [Stop]-Button will be enabled and the [Start Import]-Button will be disables correctly, but the mysql child process wont come up in the process list. Nothing will happen until i close the management window and reopen it.

How to repeat:
- Create folder "MySQL Tools" in /Applications folder
- Copy/Move MySQLWorkbench.app to /Applications/MySQL Tools
- Open WorkBench and manage a server instance
- Import a Dump to the server instance

Thank you for the bug report. The problem is that path to mysql command line client in the command generated is NOT quoted:

Running: /Users/openxs/my apps/wb.app/Contents/Resources/mysql --defaults-extra-file="/var/folders/dX/dXCzvuSlHX4Op1g-o1jIWk+++TI/-Tmp-/tmpPE6mt9/extraparams"   --host=127.0.0.1 --user=root --port=3306 --default-character-set=utf8 --comments < "/tmp/Dump20110126.sql"

When doing Export mysqldump path is quoted properly.

Noted in 5.2.34 changelog.

It was not possible to import a dump if Workbench was installed in a
directory having a name that contained spaces.