[MDEV-5528] Command line variable to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats Created: 2014-01-14  Updated: 2019-06-28  Resolved: 2014-11-04

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: 10.1.2

Type: Task Priority: Major
Reporter: Alexander Barkov Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-5377 Row-based replication of MariaDB temp... Closed
blocks MDEV-6001 Merge tests for MySQL WL#946 TIME/DAT... Stalled
Duplicate
is duplicated by MDEV-5377 Row-based replication of MariaDB temp... Closed
Relates
relates to MDEV-15228 Document how to upgrade old temporal ... Closed
relates to MDEV-19906 Show internal type for TIMESTAMP, DAT... Closed
relates to MDEV-15225 Can't import .ibd file with temporal ... Closed

 Description   

Add a new mysqld command line parameter to choose
between MariaDB-5.3 and MySQL-5.6 low level formats
for TIME, DATETIME, TIMESTAMP:

mysqld --mysql56-temporal-format

Add a corresponding read-only global system variable @@mysql56_temporal_format.

Consider switching to the MySQL56 temporal format as the default.
The advantage of the MySQL56 format is that it uses
separate type codes MYSQL_TYPE_TIME2, MYSQL_TYPE_TIMESTAMP2,
MySQL_TYPE_DATETIME2 and put the column precisions in metadata
in the binary log, which can help to fix the problem reported in MDEV-5377.



 Comments   
Comment by Sergei Golubchik [ 2014-10-17 ]

ok to push

Comment by Ian Gilfillan [ 2014-11-04 ]

This option has now been added to the documentation.

Generated at Thu Feb 08 07:05:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.