Bug #62959 Workbench doesn't handle unsaved changes properly when exiting the program
Submitted: 27 Oct 2011 7:16 Modified: 27 Jul 2012 8:29
Reporter: Karsten Wutzke Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.35 OS:Any
Assigned to: CPU Architecture:Any
Tags: exit quit save

[27 Oct 2011 7:16] Karsten Wutzke 
Description:
When exiting Workbench with an unsaved model, WB will ask the user to

* Save
* Don't save

First of all, the dialog appears *after* the main window has already been closed. BUG #1.

then the "Cancel" exit operation is not only shown differently in that dialog, but it also has no functionality. What if the user has inadvertedly invoked the exit operation? There's no way to cancel the exit and go back.

How to repeat:
Open a model, change, then exit.

Suggested fix:
-
[27 Oct 2011 9:05] Valeriy Kravchuk 
Thank you for the problem report. Verified on Windows XP.
[27 Jul 2012 8:29] Philip Olson 
Fixed as of Workbench 5.2.41, and here's the changelog entry:

Closing MySQL Workbench while editing SQL Scripts
will now prompt the user to save the edits.

See also #61037