Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
The task is to extract and backport all changes from MySQL 5.6 that move timestamp handling from the handler interface to the server.
The change was done by:
revno: 3402.50.105
committer: Martin Hansson <martin.hansson@oracle.com>
branch nick: mysql-wl5874-push
timestamp: Tue 2012-01-31 16:16:16 +0100
message:
WL#5874: CURRENT_TIMESTAMP as DEFAULT for DATETIME columns.
There is no public WL, however there is documentation:
http://dev.mysql.com/doc/refman/5.6/en/timestamp-initialization.html
First goal is to evaluate MySQL's patch, whether it makes sense to backport it, or to reimplement it.
Specifically check what are the changes to the FRM format, so that we can read MySQL 5.6 FRM files.
Additional patches to investigate:
Bug#11745578: 17392: ALTER TABLE ADD COLUMN TIMESTAMP
DEFAULT CURRENT_TIMESTAMP INSERTS ZERO
Possibly the following patch is related:
committer: Martin Hansson <martin.hansson@oracle.com>
branch nick: mysql-trunk-security
timestamp: Thu 2012-02-09 13:33:22 +0100
message:
Merge of fix for Bug#11765810.
In addition, MySQL 5.6.6 adds the following system variable, and corresponding change in behavior:
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_explicit_defaults_for_timestamp
Since MySQL 5.6.6 is not Launchpad yet, it seems that the above is implemented by the following patches:
Attachments
Issue Links
- duplicates
-
MDEV-780 LP:967396 - Datetime field does not accept default NOW()
- Closed
- relates to
-
MDEV-3939 Different behavior comparing to MySQL 5.6 on adding an auto-initialized timestamp/datetime column to InnoDB table
- Closed
-
MDEV-3929 Add system variable explicit_defaults_for_timestamp for compatibility with MySQL
- Closed
-
MDEV-26778 row_start is not updated in current row for InnoDB
- Closed