Bug #19425 Changing column order in index : no need to alter table
Submitted: 28 Apr 2006 14:32 Modified: 21 Sep 2006 13:09
Reporter: Anthony Willard (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:v1.1.9 OS:Windows (WinXP, SP2)
Assigned to: Mike Lischke CPU Architecture:Any
Tags: Object Editors

[28 Apr 2006 14:32] Anthony Willard
Description:
When editing a table and changing the sequence of columns in an index from A,B to B,A, I get the message "The changes you made did not result in the need to alter the table".  I'm using the MyISAM engine.

Logically, the sequence of columns in a key should result in change to the definition.

How to repeat:
Create a table with two char(10) columns, named A and B.

Add a primary index with A as the first key, B as the second.

Save the definition.

Edit the table definition and drag the column B to preceed A in the index, click apply, get the message.

Suggested fix:
It appears that the process is evaluating the columns in the key, not the sequence within the index.
[28 Apr 2006 15:09] Valeriy Kravchuk
Thank you for a bug report. Verified just as described.
[21 Sep 2006 13:09] Mike Lischke
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html