Bug #44458 INSERTS Editor does not allow deletes
Submitted: 24 Apr 2009 13:00 Modified: 12 Aug 2009 10:28
Reporter: Craig Fowler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S4 (Feature request)
Version:5.1.10/beta OS:Linux (Kubuntu Hardy)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: editor, insert

[24 Apr 2009 13:00] Craig Fowler
Description:
There seems to be no "remove row"/delete functionality (possibly I'm just blind and can't find it, but I tried the usuals like right-clicking for a context menu).

If I create a few inserts and then later need to remove one of them (say I changed my mind) then I can't.

My current workaround is to break the .mwb apart (thanks for using open standards: zip/XML!) and edit the .xml data file to remove the unwanted INSERT row by hand.

How to repeat:
Create a table, add some columns, go to the 'inserts' tab and then add a row or two.

Try to delete a row that was inserted.

Suggested fix:
Add slightly richer controls to the INSERTs editor.
[24 Apr 2009 13:46] Valeriy Kravchuk
In 5.1.10 on Windows there is a small text at the bottom of Inserts editor window saying:

"To remove a row, select row-header and press [Del]"

It works this way. Please, check if it works the same way on Linux.
[24 Apr 2009 14:00] Craig Fowler
Screenshot of the INSERTs editor - 5.1.10/Linux

Attachment: workbench.png (image/png, text), 23.89 KiB.

[24 Apr 2009 14:01] Craig Fowler
Sorry, it doesn't appear that way.  I upgraded from 5.1.9 to 5.1.10 and tried as you suggested.

I have attached a screenshot of how it appears on my Linux machine.
[27 Apr 2009 6:53] Valeriy Kravchuk
Indeed, on Linux this feature is missing.
[11 Aug 2009 21:48] Johannes Taxacher
right-click gives a popup-menu which offers delete
and using the delete key its also possible now to properly remove a column.
fix will be in 5.1.17
[12 Aug 2009 10:28] Tony Bedford
An entry was added to the 5.1.17 changelog:

The Inserts Editor did not have functionality to remove a row once added. This problem only occurred with MySQL Workbench running on Linux.