MySQL Bugs: #44532: New Index Creation Shows Existing Index Field Selection

Bug #44532	New Index Creation Shows Existing Index Field Selection
Submitted:	28 Apr 2009 21:59	Modified:	8 Jun 2009 14:03
Reporter:	Justin Noel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.12 Beta	OS:	MacOS
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	CHECKED, create, INDEX, workbench

Description:
When creating a new index in a table that already has indexes, the previously displayed index field is not unselected.  This causes confusion and concern that the newly created index will be on the wrong field.

How to repeat:
Open Workbench and create a new table or edit an existing table.

On the Indices tab for the current table, click the "<click to edit>" marker under the Index column.

You will be in data entry mode.  If the table already has an index, you will see that the Index Columns for the previously display index is STILL showing checked.

Suggested fix:
Do not show any previously selected indexes immediately on clicking the "<click to edit>" field.

Thank you for the problem report. Indeed, current behavior is misleading.

fixed. will be included in 5.1.13

An entry was added to the 5.1.13 changelog:

When a new index was created in the Indexes tab for a table that already had indexes, the previously displayed index field remained selected. This caused concern that the newly created index would be on the wrong field.