Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Duplicate
-
10.0(EOL), 10.1(EOL)
Description
MySQL 5.6 converts temporal types to the new sub-second-enabled type on ALTER TABLE ... FORCE (while original old types are kept when doing ALTER TABLE ... ENGINE=..., and even on CREATE TABLE ... LIKE)
MariaDB doesn't touch temporal types on ALTER TABLE ... FORCE though, here some explicit change to the table structure is needed to force a change to the new temporal implementation instead, e.g. a ADD COULUMN or MODIFY COLUMN.
The MySQL implementation of the operation was added with the following change set:
https://github.com/mysql/mysql-server/commit/cc1fd36e44c793b85b2cae0117492a34f09dbf1a
Attachments
Issue Links
- duplicates
-
MDEV-16542 Fix ALTER TABLE FORCE to upgrade temporal types
- Closed
- relates to
-
MDEV-6389 DATETIME w/ transportable tablespaces from MySQL 5.6 to MariaDB 10.0 gives "precise type mismatch" error.
- Open
-
MDEV-15225 Can't import .ibd file with temporal type format differing from mysql56_temporal_format
- Closed
-
MDEV-15228 Document how to upgrade old temporal columns
- Closed
-
MDEV-19906 Show internal type for TIMESTAMP, DATETIME, and TIME columns
- Closed
-
MDEV-11351 Not able to rebuild tables with old timestamp format
- Confirmed