MySQL Bugs: #22191: Jdbc Connection strings in the GUI

Bug #22191	Jdbc Connection strings in the GUI
Submitted:	9 Sep 2006 11:48	Modified:	11 Feb 2009 15:14
Reporter:	Dan Kloke (Candidate Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S4 (Feature request)
Version:	1.0.25	OS:	Windows (Win2000)
Assigned to:		CPU Architecture:	Any
Tags:	connection string jdbc editing

Description:
This is not strictly speaaking a bug, but in a GUI, the responsiveness of the interface is a consideration.

This applies to both the Source and Target connection panes (steps 3 and 5)

I use custom connection strings for my migrations (including "&compression=true").

One *must* fill in the Hostname and Username fields in order to enable the Next button. Filling out these areas does not fill in the connection string, one must "try" the settings and go back to the pane to get an editable connection string.

Entering the connection string without having filled out Hostname and Username doesn't enable the Next button. if a connection string is entered, Hostname and Username can be anything (but not blank), the connection string takes precedence. This is fine, but the connection string should enable the Next button.

If one selects a Stored Connection after filling out the connection string, the string is blanked out.

It might be convenient for the user to add a checkbox for the Compression option. That way the option can be saved in the Stored Connection for user convenience.

How to repeat:
At the Target or Source pane, enter a connection string.

Next is not enabled.

Suggested fix:
Enable the Next button when a connection string is entered.

Build the connection string as parameters are entered, or when a Stored Connection is selected.

Add an option to include the Compression parameter.

Just noticed that a valid connection string doesn't take precedence over other connection paramater settings, during the Reverse Engineering process. The implication is that the custom connection string is not used.

Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/