MySQL Bugs: #34819: column editing stops working after a while

Bug #34819	column editing stops working after a while
Submitted:	25 Feb 2008 20:47	Modified:	28 Mar 2008 18:42
Reporter:	randy locklair	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.13 SE Beta	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	Edit Table

Description:
after adding and renaming a bunch of foreign key columns, the table editor stopped working.  double clicking anywhere on one of the existing rows, instead of switching to an edit box, would just toggle whether or not the column was a primary key.  i'll attach an image showing what i mean.

How to repeat:
it just seemed to randomly happen after editing for a while. i am trying to reproduce the steps but maybe you can see what happened from a look in the code.

Suggested fix:
make sure you can always edit the rows.

see comment added to bug.

Attachment: bug1.jpg (image/jpeg, text), 97.59 KiB.

normally once you click on a row, you automatically get the edit box, as shown in the attached picture.  what happened for me, eventually, is clicking on the row would just highlight the whole row, no edit box.  trying to click again did nothing, and trying to double click at any time just toggled the primary key.

Please, check with a newer version, 5.0.14, and inform about the results.

OK I had just upgraded to 14--was this a known issue in 13?  I am trying to figure out a stable step by step way to recreate so I can compare the two. I will let you know what I find.

hi randy,

just to be sure - a single click on the column name (not the column symbol) should trigger the editor to open). alternatively you can press F2 on keyboard to enter editmode.
doubleclicking will only change the PK-status of that column - not start editing.

Please, inform about your findings.

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".