• Georgi Kodinov's avatar
    Bug #49838: DROP INDEX and ADD UNIQUE INDEX for same index may corrupt · d32f6b13
    Georgi Kodinov authored
       definition at engine
    
    If a single ALTER TABLE contains both DROP INDEX and ADD INDEX using 
    the same index name (a.k.a. index modification) we need to disable 
    in-place alter table because we can't ask the storage engine to have 
    two copies of the index with the same name even temporarily (if we 
    first do the ADD INDEX and then DROP INDEX) and we can't modify 
    indexes that are needed by e.g. foreign keys if we first do 
    DROP INDEX and then ADD INDEX.
    Fixed the problem by disabling in-place ALTER TABLE for these cases.
    d32f6b13
innodb_mysql.test 15.8 KB