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

Row-based replication of MariaDB temporal data types with FSP>0 into a different column type

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 5.3.12, 5.5.37, 10.0.10
    • 10.1.2
    • Replication
    • None

    Description

      Row based replication of the TIME(N), DATETIME(N) and TIMESTAMP(N)
      data types does not store column metadata into the binary log, so
      slave does not have any information about the precision of the column on
      master. Slave can only assume that the precision is exactly the same
      on master and on slave.

      This puts some limitations. Examples when RBR does not work:

      • From TIME(N) to TIME(M), for N!=M
      • From TIME(N) to another data type, e.g. VARCHAR or DECIMAL.
      • From TIME(N) in a MariaDB master to TIME(N) in a MySQL56 slave.

      Attachments

        Issue Links

          Activity

            one possible solution — use MySQL-5.6 compatible on-disk format for temporal columns by default.

            serg Sergei Golubchik added a comment - one possible solution — use MySQL-5.6 compatible on-disk format for temporal columns by default.

            See also:
            MDEV-5528 Command line variable to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats

            bar Alexander Barkov added a comment - See also: MDEV-5528 Command line variable to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats

            Just for a note,

            • From TIME(N) to another data type, e.g. VARCHAR or DECIMAL.

            This one doesn't seem to work on 5.6 either.

            elenst Elena Stepanova added a comment - Just for a note, From TIME(N) to another data type, e.g. VARCHAR or DECIMAL. This one doesn't seem to work on 5.6 either.

            It seems to be that the only reasonable solution is to use MySQL-5.6 temporal format and typecodes (that we already support anyway for compatibility reasons). Unfortunately, this cannot be done in 10.0...

            serg Sergei Golubchik added a comment - It seems to be that the only reasonable solution is to use MySQL-5.6 temporal format and typecodes (that we already support anyway for compatibility reasons). Unfortunately, this cannot be done in 10.0...

            This problem was fixed by MDEV-5528.

            bar Alexander Barkov added a comment - This problem was fixed by MDEV-5528 .

            People

              bar Alexander Barkov
              bar Alexander Barkov
              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.