[MDEV-28632] Change default of explicit_defaults_for_timestamp to ON - Jira

Ralf Gebhardt created issue - 2022-05-20 12:59

Ralf Gebhardt made changes - 2022-05-20 13:01

Field	Original Value	New Value
Link		This issue includes ~~MDEV-28470~~ [ ~~MDEV-28470~~ ]

Ralf Gebhardt made changes - 2022-05-20 13:02

Link

This issue is duplicated by ~~MDEV-28470~~ [ ~~MDEV-28470~~ ]

Ralf Gebhardt made changes - 2022-05-20 13:03

Link

This issue includes ~~MDEV-28470~~ [ ~~MDEV-28470~~ ]

Sergei Golubchik made changes - 2022-06-11 14:24

Fix Version/s

10.10 [ 27530 ]

Sergei Golubchik made changes - 2022-06-11 14:24

Status

Open [ 1 ]

In Progress [ 3 ]

Sergei Golubchik made changes - 2022-06-12 20:04

Status

In Progress [ 3 ]

Stalled [ 10000 ]

Sergei Golubchik made changes - 2022-06-12 20:04

Status

Stalled [ 10000 ]

In Testing [ 10301 ]

Michael Widenius made changes - 2022-06-14 14:02

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
<<sql>>
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

With explicit_defaults_for_timestamp=ON the result would be:
<<sql>
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

Michael Widenius made changes - 2022-06-14 14:03

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
<<sql>>
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

With explicit_defaults_for_timestamp=ON the result would be:
<<sql>
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{sql}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{sql}

With explicit_defaults_for_timestamp=ON the result would be:
<<sql>
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

Michael Widenius made changes - 2022-06-14 14:03

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{sql}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{sql}

With explicit_defaults_for_timestamp=ON the result would be:
<<sql>
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{quote}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{quote}

With explicit_defaults_for_timestamp=ON the result would be:
<<sql>
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

Michael Widenius made changes - 2022-06-14 14:04

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{quote}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{quote}

With explicit_defaults_for_timestamp=ON the result would be:
<<sql>
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
<</sql>>

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{monospace}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{monospace}

With explicit_defaults_for_timestamp=ON the result would be:
{monospace}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{monospace}

Michael Widenius made changes - 2022-06-14 14:05

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{monospace}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{monospace}

With explicit_defaults_for_timestamp=ON the result would be:
{monospace}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{monospace}

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{{monospaced}}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{{monospaced}}

With explicit_defaults_for_timestamp=ON the result would be:
{{monospaced}}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{{monospaced}}

Michael Widenius made changes - 2022-06-14 14:05

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{{monospaced}}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{{monospaced}}

With explicit_defaults_for_timestamp=ON the result would be:
{{monospaced}}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
{{monospaced}}

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{{
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
}}

With explicit_defaults_for_timestamp=ON the result would be:
{{
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
}}

Michael Widenius made changes - 2022-06-14 14:06

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{{
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
}}

With explicit_defaults_for_timestamp=ON the result would be:
{{
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1
}}

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1

With explicit_defaults_for_timestamp=ON the result would be:

CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1

Michael Widenius made changes - 2022-06-14 14:06

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1

With explicit_defaults_for_timestamp=ON the result would be:

CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ...
With explicit_defaults_for_timestamp=ON the result would be:

CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ...

Sergei Golubchik made changes - 2022-06-14 15:26

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ...
With explicit_defaults_for_timestamp=ON the result would be:

CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ...

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{code:sql}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ...
{code}
With explicit_defaults_for_timestamp=ON the result would be:
{code:sql}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ...
{code}

Sergei Golubchik made changes - 2022-06-15 10:56

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values
https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{code:sql}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ...
{code}
With explicit_defaults_for_timestamp=ON the result would be:
{code:sql}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ...
{code}

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{code:sql}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ...
{code}
With explicit_defaults_for_timestamp=ON the result would be:
{code:sql}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ...
{code}

MySQL did it in 8.0.2

Sergei Golubchik made changes - 2022-06-18 19:02

Assignee

Sergei Golubchik [ serg ]

Lena Startseva [ JIRAUSER50478 ]

Elena Stepanova made changes - 2022-06-29 18:49

Assignee

Lena Startseva [ JIRAUSER50478 ]

Elena Stepanova [ elenst ]

Elena Stepanova made changes - 2022-06-29 21:40

Link

This issue relates to MDEV-28983 [ MDEV-28983 ]

Sergei Golubchik made changes - 2022-06-29 22:39

Assignee

Elena Stepanova [ elenst ]

Sergei Golubchik [ serg ]

Sergei Golubchik made changes - 2022-06-29 22:39

Status

In Testing [ 10301 ]

Stalled [ 10000 ]

Sergei Golubchik made changes - 2022-06-29 22:39

Priority

Major [ 3 ]

Critical [ 2 ]

Sergei Golubchik made changes - 2022-07-04 17:48

Status

Stalled [ 10000 ]

In Testing [ 10301 ]

Sergei Golubchik made changes - 2022-07-04 17:48

Assignee

Sergei Golubchik [ serg ]

Elena Stepanova [ elenst ]

Sergei Golubchik made changes - 2022-07-04 17:51

Assignee

Elena Stepanova [ elenst ]

Sergei Golubchik [ serg ]

Sergei Golubchik made changes - 2022-07-04 17:55

Status

In Testing [ 10301 ]

Stalled [ 10000 ]

Sergei Golubchik made changes - 2022-07-04 18:59

Status

Stalled [ 10000 ]

In Testing [ 10301 ]

Sergei Golubchik made changes - 2022-07-04 18:59

Assignee

Sergei Golubchik [ serg ]

Elena Stepanova [ elenst ]

Elena Stepanova made changes - 2022-07-09 21:20

Link

This issue causes ~~MDEV-29074~~ [ ~~MDEV-29074~~ ]

Elena Stepanova made changes - 2022-07-09 22:16

Link

This issue causes ~~MDEV-29075~~ [ ~~MDEV-29075~~ ]

Elena Stepanova made changes - 2022-07-10 18:58

Link

This issue causes ~~MDEV-29078~~ [ ~~MDEV-29078~~ ]

Sergei Golubchik made changes - 2022-07-18 11:48

Link

This issue causes ~~MDEV-29074~~ [ ~~MDEV-29074~~ ]

Sergei Golubchik made changes - 2022-07-26 12:45

Comment

[ [~elenst], I've pushed everything into bb-10.10-~~MDEV-28632~~ branch. But after everything is ok, I'll cherry-pick commits "make @@explicit_defaults_for_timestamp session variable" and "save it in binlog, so that CREATE TABLE could be replayed correctly on the slave" to 10.3 ]

Sergei Golubchik made changes - 2022-08-01 12:59

Link

This issue is blocked by ~~MDEV-29225~~ [ ~~MDEV-29225~~ ]

Sergei Golubchik made changes - 2022-08-01 14:35

Link

This issue blocks ~~MDEV-29227~~ [ ~~MDEV-29227~~ ]

Elena Stepanova made changes - 2022-08-02 18:13

Assignee	Elena Stepanova [ elenst ]	Sergei Golubchik [ serg ]
Status	In Testing [ 10301 ]	Stalled [ 10000 ]

Sergei Golubchik made changes - 2022-08-02 20:31

Priority

Critical [ 2 ]

Blocker [ 1 ]

AirFocus made changes - 2022-08-09 16:09

Description

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values https://mariadb.com/kb/en/timestamp/#automatic-values

*explicit_defaults_for_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for_timestamp=OFF (default):
{code:sql}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ...
{code}
With explicit_defaults_for_timestamp=ON the result would be:
{code:sql}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ...
{code}

MySQL did it in 8.0.2

Users new to MariaDB often struggle with the default behavior of MariaDB regarding the datatype timestamp and automatic values https://mariadb.com/kb/en/timestamp/#automatic\-values

*explicit_defaults_for\_timestamp* , currently set to OFF by default, should be ON by default.

At the same time it should be checked if the variable can become a dynamic variable and if the scope SESSION can be added.

In effect:
With explicit_defaults_for\_timestamp=OFF (default):

{code:sql}
MariaDB> CREATE TABLE t1 (a timestamp);
MariaDB> SHOW CREATE TABLE t1;

CREATE TABLE `t1` (
`a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ...
{code}

With explicit_defaults_for\_timestamp=ON the result would be:

{code:sql}
CREATE TABLE `t1` (
`a` timestamp NULL DEFAULT NULL
) ...
{code}

MySQL did it in 8.0.2

Sergei Golubchik made changes - 2022-08-10 19:48

Fix Version/s		10.10.1 [ 27913 ]
Fix Version/s	10.10 [ 27530 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Elena Stepanova made changes - 2022-08-18 10:00

Link

This issue causes ~~MDEV-29322~~ [ ~~MDEV-29322~~ ]

Ralf Gebhardt made changes - 2023-03-21 10:44

Labels

incompatibility

Preview_10.10 incompatibility

MariaDB Server

Change default of explicit_defaults_for_timestamp to ON

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration