Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-28632

Change default of explicit_defaults_for_timestamp to ON

    XMLWordPrintable

Details

    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
      		 
      ) ...

      MySQL did it in 8.0.2

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-29227 deprecate explicit_defaults_for_timestamp=0

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29075 Changing explicit_defaults_for_timestamp within stored procedure works inconsistently

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29078 For old binary logs explicit_defaults_for_timestamp presumed to be OFF, server value ignored

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29322 ASAN heap-use-after-free in Query_log_event::do_apply_event, rpl.rpl_mdev10863 fails frequently

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          is blocked by

          Task - A task that needs to be done. MDEV-29225 make explicit_defaults_for_timestamps SESSION variable

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Task - A task that needs to be done. MDEV-28470 Please remove automatic TIMESTAMP update behaviour

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28983 TIMESTAMP logic remains partly non-standard with explicit_defaults_for_timestamp

          • Major - Major loss of function.
          • Open

          Activity

            People

              serg Sergei Golubchik
              ralf.gebhardt Ralf Gebhardt
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.