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

Command line variable to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1.2
    • OTHER
    • None

    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.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-5377 Row-based replication of MariaDB temporal data types with FSP>0 into a different column type

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-6001 Merge tests for MySQL WL#946 TIME/DATETIME/TIMESTAMP with fractional precision

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Stalled
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-5377 Row-based replication of MariaDB temporal data types with FSP>0 into a different column type

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-15228 Document how to upgrade old temporal columns

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-19906 Show internal type for TIMESTAMP, DATETIME, and TIME columns

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15225 Can't import .ibd file with temporal type format differing from mysql56_temporal_format

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

          Web Link Bug #70124 Timestamp and datetimes self-incompatible during replication

          Web Link Bug #72610 Out of memory on 5.6 slave using RBR with DATETIME when table created in 5.5.

          Activity

            Ascending order - Click to sort in descending order
            bar Alexander Barkov created issue -
            bar Alexander Barkov made changes -
            Field Original Value New Value
            Summary Command line variables to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats Command line variable to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats
            bar Alexander Barkov made changes -
            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_temoporal_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 in the binary log, which can help
            to fix the problem reported in MDEV-5377.
            		 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 in the binary log, which can help
            to fix the problem reported in MDEV-5377.
            bar Alexander Barkov made changes -
            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 in the binary log, which can help
            to fix the problem reported in MDEV-5377.
            		 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.
            serg Sergei Golubchik made changes -
            Fix Version/s 10.1.0 [ 12200 ]
            serg Sergei Golubchik made changes -
            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.
            		 Add a new mysqld command line parameter to choose
            between MariaDB-5.3 and MySQL-5.6 low level formats
            for TIME, DATETIME, TIMESTAMP:
            {noformat}
            mysqld --mysql56-temporal-format
            {noformat}
            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.
            serg Sergei Golubchik made changes -
            Workflow defaullt [ 32901 ] MariaDB v2 [ 43349 ]
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Fix Version/s 10.1 [ 16100 ]
            Fix Version/s 10.1.0 [ 12200 ]
            bar Alexander Barkov made changes -
            Assignee Alexander Barkov [ bar ] Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] In Review [ 10002 ]
            serg Sergei Golubchik made changes -
            Status In Review [ 10002 ] Stalled [ 10000 ]
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ] Alexander Barkov [ bar ]
            bar Alexander Barkov made changes -
            Status Stalled [ 10000 ] In Progress [ 3 ]
            bar Alexander Barkov made changes -
            Assignee Alexander Barkov [ bar ] Ian Gilfillan [ greenman ]
            greenman Ian Gilfillan made changes -
            Component/s OTHER [ 10125 ]
            Fix Version/s 10.1.2 [ 15801 ]
            Fix Version/s 10.1 [ 16100 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            bar Alexander Barkov made changes -
            ratzpo Rasmus Johansson (Inactive) made changes -
            Workflow MariaDB v2 [ 43349 ] MariaDB v3 [ 65262 ]
            GeoffMontee Geoff Montee (Inactive) made changes -
            GeoffMontee Geoff Montee (Inactive) made changes -
            bar Alexander Barkov made changes -
            GeoffMontee Geoff Montee (Inactive) made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 65262 ] MariaDB v4 [ 132248 ]

            People

              greenman Ian Gilfillan
              bar Alexander Barkov
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.