MySQL Bugs: #36190: No way to save Forward Engineering data

Bug #36190	No way to save Forward Engineering data
Submitted:	17 Apr 2008 22:55	Modified:	16 Oct 2009 7:25
Reporter:	Martin Gara	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.0.19 SE rev 3067	OS:	Windows (Win2K)
Assigned to:		CPU Architecture:	Any
Tags:	CHECKED

Description:
When you forward engineer a database you can determine variour parameters such as what will be generated (scripts, etc.), what won't be generated (exclusions) and where it will be generated (target database connection) but unfortunately you cannot save all the configuration data for next time (or for a Synchronize e.g connection data).

How to repeat:
Perform a forward engineer of a database.
Observe that there is no option for saving the forward engineering config data.
Perform another forward engineer of the database and observe that you must enter (as well as remember) the same stuff as last time.
Perform a Synchronize and observe that you are asked again for the connection data.

Suggested fix:
Allow the Forward Engineering (FE) data to be saved to a file (.mw?) at any point in the FE process - the reason being that you may not be able to complete the whole FE process, so a final save may not be so useful (validation problems may intervene). At the very least allow the data to be save at the Run Validation point.

Thank you for a reasonable feature request.

To make this request really useful, it would be a good idead to be able to store the 'configuration' for re-use via a hotkey/toolbar/menu entry of some kind.

This would allow for repeated invocations of the same operation, without having to go through all of the 'wizard' steps each time. It would also make it possible to choose from several configurations, depending on the context of your current work - deploying to a development web application database instance, or deploying to an automated test script database instance (These often differ only by connection details)

This is a duplicate of bug #34977