Bug #36262 | Online alter table doesn't support "after <field>" | ||
---|---|---|---|
Submitted: | 22 Apr 2008 19:26 | Modified: | 7 Jun 2012 9:11 |
Reporter: | Jim Starkey | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: DDL | Severity: | S3 (Non-critical) |
Version: | 6.0-falcon | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[22 Apr 2008 19:26]
Jim Starkey
[25 Apr 2008 7:47]
Sveta Smirnova
Thank you for the report. Verified as described.
[7 Oct 2008 20:36]
Konstantin Osipov
Will be fixed when we have an engine that actually supports online ADD COLUMN.
[7 Jun 2012 9:11]
Dmitry Lenev
Hello! This issue has been fixed as part of work on new Online ALTER table API in 5.6 series of server. Now SQL-layer calls handler::check_if_supported_inplace_alter() method, which corresponds to handler::check_if_supported_alter() in old Falcon tree, even if columns are added and/or moved around. This change should become available as part of 5.6.6 milestone release. Since this bug was never relevant for any GA/stable version of MySQL Server there is nothing to document and I am simply closing this bug report.