MySQL Bugs: #51965: Result set refreshed after entry of primary key data using Edit Table Data

Bug #51965	Result set refreshed after entry of primary key data using Edit Table Data
Submitted:	11 Mar 2010 18:44	Modified:	12 May 2010 15:58
Reporter:	Cecil Carpenter	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.16 Beta	OS:	Linux (Ubuntu 9.10)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	Edit Table Data New Row Primary Key Column

Description:
Whenever you choose edit table data, the EDIT command is executed, returning a result set in primary key sequence (assuming there is a primary key)

If the first column is the primary key, after entering data into that column, the result set is refreshed when you hit a key such as tab or enter or click with the mouse, even though no other data has been entered. You then must scroll to the bottom of the result set to continue entering your data.

How to repeat:
(1) Right click a table in the database table list pane or in the overview pane;
(2) Select Edit Table Data;
(3) Execute the Edit statement;
(4) Scroll to the bottom of the result set;
(5) Click in the first column of the row below the last result set row;
(6) Enter data in primary key column;
(7) Press Enter or Tab, or click in another column with mouse.

Suggested fix:
Correct code to not refresh result set.

Thank you for the bug report.

Position of recordset is now kept unchanged.
Note: Whether the 1st column is a PK or not does not matter.

fix confirmed in repository

An entry has been added to the 5.2.21 changelog:

When editing table data in the SQL Editor, the table would refresh after data was edited in the first column. This meant it was necessary to then scroll to the bottom of the table data to continue editing the record.