MySQL Bugs: #49921: Enhance Forward Engineer Connection Option

Bug #49921	Enhance Forward Engineer Connection Option
Submitted:	24 Dec 2009 17:13	Modified:	30 Aug 2012 19:19
Reporter:	Mike Frank	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.11	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
When forward engineering and “using existing”

Changes here change the connection
This was a surprise.  Shouldn’t change.  

How to repeat:
fwd engineer and in the connection options dialog select connection and then change the Default schema.

Suggested fix:
Need schema selector list.

Maybe have radio – use default, or select schema.

Shouldn’t need to create a connection for every schema.

Thank you for the problem report.

talked with mike frank about this issue and it it turns out we'd re-work the design of the connection screens in wizards.
first - remove the "default schema" textbox (as this property is not used in fwd/rev-eng or sync processes), 
second - move the "manage stored connection" out of the "stored connection" dropdown; make it a separate button.
third - remove the details of the connections; so one can either select a stored connection from the dropdown or create/modify one via the "manage ..." button.
this should clear up the connection step quite a bit

Fixed as of 5.2.43, and here's the changelog entry:

While using the "Forward Engineer" wizard, any
change detected in a connection option now clears the "Stored
connection" field.