MySQL Bugs: #49403: "Fetch All" disappears randomly

Bug #49403	"Fetch All" disappears randomly
Submitted:	3 Dec 2009 14:53	Modified:	20 Jun 2011 18:54
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.10 r4680	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
I have a table with more than 1000 rows, and when I edit this table, I see the "Fetch All" option.  This option continues to exist for me after I do any one of the following:

* Sort the result set by columns
* Edit an existing row
* Add a new row

However, when I add a new row and then sort the records by column, without first commiting or rolling back, the "Fetch All" option disappears.

I can understand not allowing "Fetch All" when uncommited changes have been made, and indeed, an error is given when this is used in such a context:

There are pending changes. Please commit or rollback first.

(it might be useful to change this text or the tooltips for "Apply made changes to data source" /  "Discard made changes to data" so that it is clear what action should be taken)

It is odd to leave "Fetch All" available, yet warn users in some contexts, yet remove it completely in combinations of the same.

How to repeat:
See above.

Suggested fix:
See above.

Noted in 5.2.34 changelog.

For data browsing, the Fetch All option sometimes disappeared.