Bug #35613 Double-Clicking on column-editor row toggles primary key instead of editing
Submitted: 27 Mar 2008 15:10 Modified: 9 May 2008 7:44
Reporter: Daniel Haas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Alfredo Kojima CPU Architecture:Any

[27 Mar 2008 15:10] Daniel Haas
Description:
Editing columns is really cumbersome, because when you double-click on the row of a column toggles the primary key property instead of entering edit-mode in the field below the mouse. For example when you want to change the name of a field, you have to click two times with a pause to select the field and be able to enter something. - For the name F2 also works, but for other fields like default value or datatype it does not work.
So I accidentally always toggle the primary-key status of a columnd when trying to modify it.

How to repeat:
1. Add a table
2. Add a column
3. Try to rename the column with a double-click on the name of the column.

Suggested fix:
The primary-key attribute should only be changed by a double-click on the icon infront of the column. When double-clicking somewhere else in the row, the corresponding field under the mouse should enter into edit-mode.
[27 Mar 2008 16:44] MySQL Verification Team
Thank you for the bug report.
[28 Mar 2008 11:44] Johannes Taxacher
fixed as described. tested with SVN Rev 2888
[28 Mar 2008 17:25] MC Brown
A note has been added to the 5.0.16rc changelog: 

When double clicking on the row in a column as a primary key, the primary key property would be toggled. The editor will now allow you to edit the value when clicking on a data row on the table.
[7 Apr 2008 8:31] Daniel Haas
I cannot see this fixed in rev 2911.
Double-Clicking on the column name or default value of a column in the column editor still toggles the primary key attribute and the NotNull flag.
This is also reported in this bug: http://bugs.mysql.com/bug.php?id=35841
[8 Apr 2008 13:37] Johannes Taxacher
please, could you verify if this is still an issue with the latest version (5.0.17, Rev
2972) ... i cant reproduce it in latest versions.
[8 May 2008 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[9 May 2008 7:44] Daniel Haas
Sorry for not responding, I forgot about the bug.
I tested this in 5.0.21 OSS and can confirm that this bug is fixed, so I close it.