MySQL Bugs: #51373: More control when you open sql files from sqleditor

Bug #51373	More control when you open sql files from sqleditor
Submitted:	22 Feb 2010 6:38	Modified:	16 Apr 2010 19:28
Reporter:	Carlos Pereira	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.2.16 OSS Rev 5249	OS:	Windows (XP SP3 Spanish)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	control sql files, SQL, sql editor, sql files

Description:
Hi developers

When you open a SQL file from SQL Editor the file loads perfectly!!!

But when you make some changes to the text and when you press the save button from toolbar the application don´t remember the file that was loaded and show the save as dialog. The normal option is that after you press the button the file is overwritten automatically!!!

I think that the sql editor may work like a text editor!!! and try to control loaded files like a text editor!!!

Thanks for all and is only a suggestion!!!

How to repeat:
Open a sql file and then try to safe!!!

The app show the save as dialog and the file may be overwrite!!!

Suggested fix:
That the sql editor write the file without user interaction or could be an option for the preferences zone!!! This option could be: How to save open files: show save dialog, overwrite the file!!!

I have to agree other point:

SQL editor don't make some distintion between save and save as option from file menu!!! SQL editor don't see the changes!!! Undo and Redo options from Edit menu are unable for sql text editor!!!

i'd consider that being a bug because thats not expected behaviour of an app. Of course, "Save" should simply write changes back to original file and "save as.." should ask for new filename

Remembering filenames when saving/loading and tracking changed state has been fixed recently.

this is a duplicate of bug #50055