Bug #50055 | Saving an existing SQL script prompts for a new name | ||
---|---|---|---|
Submitted: | 4 Jan 2010 15:01 | Modified: | 21 Apr 2010 13:14 |
Reporter: | Simon Hambly | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.11 beta | OS: | MacOS (10.5.8) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[4 Jan 2010 15:01]
Simon Hambly
[14 Apr 2010 1:36]
Alfredo Kojima
1 and 3 have been fixed, I'm opening a new bug report for 2 (bug #52799)
[16 Apr 2010 16:58]
Johannes Taxacher
fixes as noted by dev confirmed in repository
[16 Apr 2010 19:28]
Johannes Taxacher
Bug #51373 has been marked as duplicate of this one
[21 Apr 2010 13:14]
Tony Bedford
An entry has been added to the 5.2.19 changelog: MySQL Workbench appeared to perform a Save As operation rather than a Save operation when saving a modified script file in the SQL Editor. Also, there was no indication that the file being worked on had unsaved changes (this is normally indicated by '*' in the title bar). Finally, the filename was not displayed on the SQL Editor tab.