MySQL Bugs: #50213: WorkBench doesnt run backups if there is a space in the password

Bug #50213	WorkBench doesnt run backups if there is a space in the password
Submitted:	10 Jan 2010 15:33	Modified:	2 Feb 2010 14:41
Reporter:	kgh jhg	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	MySQL Workbench 5.2.11	OS:	Windows (2003/2008)
Assigned to:	Alexander Musienko	CPU Architecture:	Any
Tags:	space in password

Description:
Workbench can connect and see database with name and password with a space in it, but cannot run backups.  The mysql code for the backup shows the password  -p section to be incorrect as the space seems to confuse it.

Running it with a name password combo without spaceing works fine.

How to repeat:
'username', 'pass word' wil be able to access workbench but fail on backup.
'username','password' will work fine.

Many thanks for writing a bug report.

There is mysqldump working in background and the following is necessary:

mysqldump --u myuser --password=pass word <--- this will fail
mysqldump --u myuser --password='pass word' <--- this will work

For the upcoming version our developers already implemented quotes around the password but then we have the problem that also somebody could use quotes as password ....

The solution is not such easy as it looks like.

We are working on it ...

Bug #49977 is set as duplicate of this bug here.

fix confirmed. will be included in 5.2.16

An entry has been added to the 5.2.16 changelog:

It was possible to connect to a database using a password containing a space. However, when this connection was used to attempt a backup the operation failed, due to the password not being correctly quoted.

I am aware that this is old bug, but it seems that 7 years later Workbench does not accept exclamation mark in the password (!) when doing connection over tunnel. I am experiencing this on MacOS, Workbench version 6.3.9.

Please ignore my last comment, it was two users defined with different passwords, on localhost and on 127.0.0.1 doing all this mess.