MySQL Bugs: #13350: Save on Close functionality

Bug #13350	Save on Close functionality
Submitted:	20 Sep 2005 13:04	Modified:	28 Apr 2006 14:25
Reporter:	Mike Willbanks	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S3 (Non-critical)
Version:	1.0.2	OS:	Windows (Windows XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
One big major thing that is missing is a save on close (although it might be in the application, it does not show... possibly because of an error).  There should be a prompt to save if the model has not been saved and/or if it has been changed and not saved.

How to repeat:
Start a new model, create a table, exit program.

Suggested fix:
Check to see if the model has been changed or not saved,
prompt user to either save or discard changes,
save and exit or exit.

Agree with Mikes comment, would be "nice" to add it to the design dialogs (eg table designer). It may just be unfamiliarity with your user interface, but its a pain when completing a table to loose all the changes due to my incompetance in not pressign 'apply changes'.

Mebbe its just a familairty thing.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Both cases are now implemented: changes in individual editors as well as in the entire model.