Bug #77175 Parsing Error for Connection Manager in Workbench
Submitted: 27 May 2015 20:28 Modified: 20 Jan 2017 19:20
Reporter: Michael Munger Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2.3 OS:Linux (Debian Jessie)
Assigned to: CPU Architecture:Any

[27 May 2015 20:28] Michael Munger
Description:
When creating a new entry in the connection manager (CLick the plus, then enter the relevant informationa bout hte connection), if you use a forward slash in the name, it will create two separate entries.

Example:
"Production Server (GA / TX)" will produce one connection for "Production Server (GA " and one additional connection for "TX)", which is nested inside first.

It appears to be a simple parsing problem. 

How to repeat:
Create a new server connection to an arbitrary server, but call it: "Production Server (GA / TX)"

Suggested fix:
Easiest thing to do would be to forbid special characters used for parsing from the input fields. Don't allow "/" and nothing else needs to be fixed.

Better thing to do would be to fix the parser. There are a number of ways to do this. It's really up to the developer to use Occum's razor.
[27 May 2015 22:08] MySQL Verification Team
Thank you for the bug report.
[28 May 2015 12:36] Mike Lischke
Actually, this is by intention. Don't use a forward slash in your connection name. This char is used to denote connection groups.
[29 Jun 2015 1:00] Bugs System
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".
[20 Jan 2017 19:20] Christine Cole
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.9 release, and here's the changelog entry:

The slash character (/) when used in the name of a new connection
separated a group from the real connection name by default without first
notifying the user. This fix gives the user an option to keep the slash
character and create a connection group or to replace all slash characters
in the connection name with underscore characters.

Thank you for the bug report.