MySQL Bugs: #66091: Selected index row changes when selecting the index type while modifying a table

Bug #66091	Selected index row changes when selecting the index type while modifying a table
Submitted:	30 Jul 2012 18:05	Modified:	21 Aug 2012 14:56
Reporter:	Bob Dankert	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.41	OS:	Windows (W7 32)
Assigned to:		CPU Architecture:	Any
Tags:	ALTER TABLE, create, Index type, mouse, row switch

Description:
When altering or creating a table, after selecting the index type from the drop down (using the mouse) the selected index row switches to the first row (the first index in the table).  This behavior does not occur when using the keyboard to select the row.

How to repeat:
1. Alter or create a table and go to the indexes tab.
2. If the table does not already have at least one index, add the first index.
3. Add an additional index.  After selecting the index type using the mouse, the active/selected index row will switch to the first index in the table.  You have to re-select the index you are editing/creating to set the fields for the index.

Suggested fix:
The index row should not change after clicking an index type.

I just upgraded to 5.2.41 and noticed that this bug has been fixed.  Closing the bug (although it may be a duplicate, my search did not find an existing bug)

I've found that this is indeed still a problem.  To replicate, follow these steps:

Create this table:

CREATE TABLE `test1` (
  `id` int(11) NOT NULL,
  `field1` varchar(45) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

In workbench, alter the above table and go to add a new index.  Enter the index name, select the index type, and the selected index row will change to the first index, which is Primary.  You have to re-select the new index you are adding.

I can not repeat this on Windows XP.

Yes, now I am not able to replicate it again.  I'm not sure why it is so finicky.

Hello Bob.
Please feel free to re-open this bug as soon as you can reproduce it.
Thanks