MySQL Bugs: #2639: Inconsistant use of the save button (floppy disk)

Bug #2639	Inconsistant use of the save button (floppy disk)
Submitted:	4 Feb 2004 3:55	Modified:	1 Jun 2004 0:38
Reporter:	Ronan O'Connor	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQLCC	Severity:	S3 (Non-critical)
Version:	0.9.4	OS:	Linux (Fedora(core1) gnome 2.4)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
The save button is used in 2 different contexts for certain windows. Compare the "Edit Table" window with the Table "Query Window" or even the "Field Editor" window (for fields of type Text). 
In the "Edit Table" window the save button is used to save changes to the database whereas in the other 2 windows mentioned above it is used to save data to a file. This is somewhat confusing.

As an aside: 
I find the use of the save button in the "Field Editor" window to be especially confusing. Since you are not allowed edit a text field directly in the Table "Query Window", (something I find mildly annoying in itself :), you must pop up the "Field Editor" window. Its an automatic reaction on my part to go for the save button, (Especially when combined with bug #2456) to save my changes, but this does a save to disk...

How to repeat:
Open an "Edit Table" window and a Field Editor window and compare save button functionality.

Hi!

MySQLCC has been discontinued and will not be developed nor maintained anymore with the exception of Critical bugs.

In the near future we will release the substitute of MySQLCC called MySQL Query Browser.