Bug #40356 Accidentally Losing Table Inserts
Submitted: 27 Oct 2008 18:51 Modified: 19 Jul 2009 1:00
Reporter: william jaspers Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.26 OS:Windows (XP SP3; .NET 3.5 SP1)
Assigned to: CPU Architecture:Any
Tags: CHECKED, EER, inserts, pre-load tables, tables

[27 Oct 2008 18:51] william jaspers 
Description:
I accidentally pushed 'ESC' on the keyboard, which closed my 'Inserts' window.
Upon re-opening the 'Inserts' window, my data was gone.

How to repeat:
Press 'ESC' after filling in several insert rows for a table.
The window should close.
Re-open the inserts window and you will find your data is gone.

Suggested fix:
After each row is completed; OR the cursor shifts to the next tuple, AUTOMATICALLY save this data.
[27 Oct 2008 19:28] MySQL Verification Team 
Thank you for the bug report.
[30 Oct 2008 19:43] Johannes Taxacher 
for 5.0 we will introduce a confirmation dialog if user cancels having active changes.
[17 Mar 2009 13:45] Susanne Ebrecht 
This is not a bug. Feature request here is to use ESC to get out of edit modus and second ESC will close all.
[17 Mar 2009 14:05] william jaspers 
I agree that ESC is and should be intended to close a modus; however, if you have made changes to the inserts (or pre-loaded data), a confirmation dialog should ask whether or not you want to save your changes. 

It just becomes a nuisance to re-enter all the data that was skipped simply because I pushed ESC rather than an OK/Save button. Although I may not be pre-loading many rows, some tables may have several columns, which can be really aggrevating to re-key.
[19 Mar 2009 13:11] Susanne Ebrecht 
Bug #41983 is set as duplicate of this bug here.
[19 Jul 2009 1:00] Alfredo Kojima 
This bug does not apply anymore as the INSERTs editor has been reimplemented in 5.2.