Comments - MariaDB 10.1.2 Release Notes
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
if you've come here because you end up with columns in the same table with two different temporals type (create-table on 10.0.xx, add new column after upgrade to 10.1.xx) and need to import those tablespaces (for example with innobackupex for backups which will obviously break!):
as you might found out: on mysql you are able to force temporal upgrade with:
alter table xy force;but not on mariadb! you need to alter EACH column:alter table xy modify foo datetime not null, ....;give me back this week of useless debugging!
reference:
https://jira.mariadb.org/browse/MDEV-9967
https://www.percona.com/blog/2016/04/27/upgrading-to-mysql-5-7-focusing-on-temporal-types/
http://mysqlserverteam.com/how-to-easily-identify-tables-with-temporal-types-in-old-format/
http://mechanics.flite.com/blog/2014/05/01/upgrading-temporal-columns-from-mysql-5-dot-5-to-mysql-5-dot-6-format/