Bug #38639 Can't delete index of type FOREIGN
Submitted: 7 Aug 2008 19:02 Modified: 22 Aug 2008 15:17
Reporter: Łukasz Palka Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.0.23 OS:Windows (XP)
Assigned to: Alfredo Kojima CPU Architecture:Any

[7 Aug 2008 19:02] Łukasz Palka
Description:
Index present on 'Index' tab with 'Type' FOREIGN can't be deleted. If foreign key with the same name on 'Foreign Keys' tab exist, index can be deleted by deleting coresponding foreign key. But if there is no foreign key with this name, index can't be deleted.

This index in sql export script looks like this:
INDEX index2 () ,

How to repeat:
1. File/New.
2. Add Table.
3. Select 'Indexes' tab.
4. Type a name of index and choose a type of FOREIGN.
5. Try to delete this index.
[7 Aug 2008 19:47] Valeriy Kravchuk
Thank you for a bug report. Verified just as described.
[8 Aug 2008 17:59] Alfredo Kojima
You can now change the index type from FOREIGN to something else so that the incorrectly created index can be deleted (or fixed)
[11 Aug 2008 6:11] Łukasz Palka
It is not possible to change the index type from FOREIGN to something else. Tested on two different Windows XP.
[11 Aug 2008 14:49] Alfredo Kojima
Sorry, I meant that the index type will be changeable in the next release. The current release does
not allow that as you have noticed.
[14 Aug 2008 11:09] Johannes Taxacher
fix confirmed. its now possible to change the index from FOREIGN to something else. Usuallly WB manages FOREIGN keys automaticly - this is meant for advanced editing only.
fix is incorporated in 5.0.24
[22 Aug 2008 15:17] Tony Bedford
An entry was added to the 5.0.24 changelog:

Indexes listed when the Index tab was selected could not be deleted if the index type was FOREIGN.
[28 May 2009 14:08] Stas Trefilov
The bug reappeared in ~ 5.1.10. currently it is impossible to change the type of FOREIGN index or delete it in both 5.1.12 and 5.2.1

mac os x 10.5.7
[29 Jan 2010 11:55] Julien Lanfrey
I can see the bug in 5.2.14b.
(Windows Vista)