MySQL Bugs: #53787: Changing the index type via 'Alter Table' don't work

Bug #53787	Changing the index type via 'Alter Table' don't work
Submitted:	19 May 2010 8:23	Modified:	27 May 2010 10:31
Reporter:	Anders Stalheim Øfsdahl	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.21	OS:	Windows (Windows 7)
Assigned to:	Alexander Musienko	CPU Architecture:	Any
Tags:	INDEX

Description:
Trying to change an index from 'INDEX' to 'UNIQUE' via 'Alter Table...' no changes is applied when clicking Apply, instead you get the error 'No changes to object were detected.'

How to repeat:
1) Create a simple table:

CREATE TABLE `test` (
  `id` INT NOT NULL AUTO_INCREMENT ,
  `column` VARCHAR(45) NULL ,
  PRIMARY KEY (`id`) ,
  INDEX `index_column` (`column` ASC) );

2) Use Object Browser and find the created table 'test', right click and select 'Alter Table...'

3) Go to the "Indexes" tab and change the index type on "index_column" from INDEX to UNIQUE, then click Apply. The error will show in the bottom left dialog window.

Suggested fix:
Change how the comparison of changes is done, to reflect changes done on index types as well.

fix confirmed in repository

An entry has been added to the 5.2.22 changelog:

In the SQL Editor, when attempting to change an index from INDEX to UNIQUE using the Alter Table dialog, no changes were applied, and the following error message was generated: No changes to object were detected.

I am using 5.2.28 and it is till a problem.

I am using 5.2.28 and it is still a problem.

I just noticed that the platform its been reported on is different to mine.
I am running MySQL Workbench CE for Linux/Unix version 5.2.28 on Ubuntu 10.04.1 64bit

The bug is still open in version 5.2.28 for Linux (Ubuntu 10.04 LTS Lucid Lynx)

Hi

I'm on Ubuntu 10.04 64bit, using MySQL Workbench 5.2.27, and this bug is still present.

Michael