Bug #54456 Commiting inserts fails silently under certain conditions
Submitted: 12 Jun 2010 11:13 Modified: 17 Jun 2010 11:14
Reporter: Tobias Minich Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.22 OS:Linux (Gentoo)
Assigned to: Alfredo Kojima CPU Architecture:Any

[12 Jun 2010 11:13] Tobias Minich 
Description:
Under the conditions described below, mysql-workbench can no longer commit inserts in the model editor.

How to repeat:
- Open a EER Diagram
- Open a table with a double-click
- In the table editor, switch to the Inserts tab
- Open a different table with a double-click
- Add a new row to the table (in the already open Inserts tab of the second table)
- Press the commit button
-> Nothing happens. The status still shows the lingering insert and if you try to change the edited table or refresh the inserts view, mysql-workbench warns you about uncommitted inserts. There seems to be no way to fix that beyond restarting mysql-workbench and loosing the rows you added.
[14 Jun 2010 15:00] MySQL Verification Team 
Thank you for the bug report.
[16 Jun 2010 14:12] Alfredo Kojima 
fixed
[16 Jun 2010 21:44] Johannes Taxacher 
fix confirmed in repository
[17 Jun 2010 11:14] Tony Bedford 
An entry has been added to the 5.2.23 changelog:

In the Inserts tab of the Table Editor, adding a new row and applying changes did not have any effect.