Bug #61037 Please implement either autosave or warning of unsaved changes in script editor
Submitted: 3 May 2011 9:54 Modified: 19 Jul 2012 6:55
Reporter: Craig Fowler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S4 (Feature request)
Version:5.2.33 OS:Linux (Debian Testing, 64-bit using Ubuntu 10.10 .deb package)
Assigned to: CPU Architecture:Any
Tags: script, UI

[3 May 2011 9:54] Craig Fowler 
Description:
To avoid ambiguity, this refers to the "SQL Scripts" stored inside of a Workbench model project, not the main SQL IDE.  I'm talking about the "SQL Scripts" listing towards the bottom of the "Model" home-page.

When editing/saving SQL scripts inside a WB model file (such as handy scripts that are associated with a project file) there are "Apply Changes" and "Discard Changes" buttons below the edit pane.  If you make changes in this pane and forget to click "Apply Changes" and then close the pane, all changes are lost.

Could I ask for either some kind of autosave/auto-apply functionality OR a warning on unsaved/un-applied changes please?  This will lower the amount of loud profanity in my office when I open a script that I want to come back to and find that it's blank/empty because when I initially pasted it in, I forgot to click "Apply changes" and it never saved :)

How to repeat:
N/A - feature request
[10 May 2011 8:54] Valeriy Kravchuk 
Thank you for the feature request.
[16 May 2011 20:35] Alfredo Kojima 
bug #61160 is a duplicate
[23 May 2011 3:33] Alfredo Kojima 
As a workaround, do a find/replace from newQuery to newFile in main_menu.xml and dbquery_toolbar.xml
[24 May 2011 0:14] Alfredo Kojima 
Disregard last 2 messages, this is about scripts attachments to a model, not SQL Editor.
[19 Jul 2012 6:55] Philip Olson 
This has been fixed as of the soon-to-be-released 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.