Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
10.1.6-2, 10.1.8-1, 10.1.8-2
Description
As the description of the main task MDEV-452 already mentions, MySQL implementation has the variable explicit_defaults_for_timestamp which modifies the behavior of auto-updated temporal columns. Since the planned release approaches and we don't have the variable yet, we either need to add it now, or decide to release without it, and add it in further versions. Either is okay as long as it's not completely forgotten.
The definition of MySQL's implementation can be found here:
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_explicit_defaults_for_timestamp
What we should do in MariaDB:
- Add this new variable and have it work as MySQL when enabled.
- Have it disabled as default, to not cause incompatibilities with old applications
- Always keep the variable around (not make it deprecated) as we don't want to have it default.
- Add a MYSQL mode where, if enabled, this variable is set.
TODO: check how replication of this variable works in MySQL.
Attachments
Issue Links
- blocks
-
MDEV-8455 Make explicit_defaults_for_timestamp dynamic
- Open
- duplicates
-
MDEV-5994 MySQL WL#6292 - Make TIMESTAMP columns nullable by default
- Closed
- is blocked by
-
MDEV-7824 [Bug #68041] Zero date can be inserted in strict no-zero mode through a default value
- Closed
-
MDEV-7831 Bad warning for DATE_ADD(timestamp_column, INTERVAL 10 SECOND)
- Closed
-
MDEV-8441 Bad SHOW CREATE TABLE output for a table with a virtual column
- Closed
- is duplicated by
-
MDEV-5836 MySQL WL#6292 - Make TIMESTAMP columns nullable by default
- Closed
- relates to
-
MDEV-452 Add full support for auto-initialized/updated timestamp and datetime
- Closed
-
MDEV-28983 TIMESTAMP logic remains partly non-standard with explicit_defaults_for_timestamp
- Open
- links to