You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG#17246318: ALTER TABLE SHOULD NOT ALLOW CREATION OF TABLES
WITH BOTH 5.5 AND 5.6 TEMPORALS
Analysis
--------
'ALTER TABLE' allows creation of tables containing temporal
columns of both mysql-5.5 and mysql-5.6 format.
Recreating tables having both 5.5 and 5.6 temporals becomes
tedious process when the metadata file(.frm) for the table
is unavailable. This would involve recreating the table having
the old temporal columns using 5.5 server instance and then
adding the 5.6 temporal columns using 5.6 server instance.
Also recreating tables having 5.5 temporals and 5.6 INNODB
FULLTEXT indexes has to follow the same process.
Currently operations are supported on the old temporal columns.
The old temporal columns are upgraded to the new format only
when they are altered(like renaming the old temporal column)
else they are retained in the old format.
In order to overcome the above mentioned tedious process
and use the space efficient new temporal format, the old
temporal types are upgraded for certain ALTER TABLE
operations listed in the fix info.
Fix info:
---------
The columns of old temporal types of mysql-5.5 are upgraded to
mysql-5.6 format when ALTER TABLE requests ADD/CHANGE/MODIFY
COLUMN, ADD INDEX or FORCE operation.
Since such conversion cannot be done using INPLACE algorithm,
the attempt to use ALGORITHM=INPLACE clause in such ALTER TABLE
for a table with mysql-5.5 temporals leads to an error.
Also a 'NOTE' is reported to indicate the upgrade of the
old temporal columns to the new format under the above
condition.
0 commit comments