[MDEV-9967] Convert old temporal types on ALTER TABLE ... FORCE Created: 2016-04-21 Updated: 2019-06-28 Resolved: 2018-11-27 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Alter Table, Temporal Types |
| Affects Version/s: | 10.0, 10.1 |
| Fix Version/s: | 10.4.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Hartmut Holzgraefe | Assignee: | Alexander Barkov |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | upstream | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| 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 |
| Comments |
| Comment by Hartmut Holzgraefe [ 2016-04-26 ] |
|
Bug description modified, removed the part about "online operation" |
| Comment by Hartmut Holzgraefe [ 2016-04-26 ] |
|
Adding or modifying a column also doesn't force a temporal type change in MariaDB, so every temporal type needs to be converted manually ... |