MySQL Bugs: #85936: SQL editor tabs created by the Navigator will not prompt to save on closing

Bug #85936	SQL editor tabs created by the Navigator will not prompt to save on closing
Submitted:	13 Apr 2017 15:02	Modified:	12 Feb 2018 11:02
Reporter:	Peter Shillito	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	6.3.10	OS:	Windows (Windows 7)
Assigned to:		CPU Architecture:	Any
Tags:	closing, save, Saving, tabs

Description:
This bug is similar as bug #58899 for version 5.2.30, however it seems to have reoccurred for version 6.3.9.

In MySQL Workbench, there are two distinct types of SQL Editor tabs that are relevant to this bug:
1) SQL File: created empty either by File->New Query Tab (or Ctrl+T) or by right clicking an item in the Navigator (such as a table) and then selecting one of the "Send to SQL Editor" options. The tab will be labelled "SQL File (number)".
2) Select only: Right clicking an item (e.g. a table) in the Navigator and then clicking the top option, which is "Select Rows" and then, depending on the settings, possibly followed by " - Limit (number)". The tab will be labelled with the table name.

Upon closing a tab after changing the contents of either kind of tab, the expected outcome is that a prompt will be displayed warning the user that there are unsaved changes.

For "select only" tabs, this prompt does not appear and the tab simply closes. In addition, the asterisk used to indicated unsaved changes on a tab does not appear in this instance.

How to repeat:
- Right click a table
- Click "Select Rows" with a limit of any number
- Make changes to the SQL query.
- Close the tab

Note the lack of a save changes prompt

Suggested fix:
Make all tabs act the same.

Thank you for the bug report. Verified on MAC OSX.

Can confirm that the bug is still present in 6.3.10