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

DATE -> DATETIME replication conversion not working, even in ALL_NON_LOSSY mode

Details

    Description

      When having a DATE column on the master, a DATETIME column on the slave, and binlog_format=ROW, inserting into the table fails on the salve with:

      Last_SQL_Error: Column 1 of table 'test.t1' cannot be converted from type 'date' to type 'datetime'

      even with slave_type_conversions=ALL_NON_LOSSY, even though a conversion from a DATE to a DATETIME should be a lossles operation.

      In the MySQL 5.6 manual this conversion is listed as "not supported before 5.5.3". In the 5.7 and 5.8 versions of the manual this paragraph has been removed, but still DATE and DATETIME are missing from the list of supported operations.

      Our own documentation doesn't seem to mention supported conversion types at all.

      https://dev.mysql.com/doc/refman/5.6/en/replication-features-differing-tables.html

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Elena Stepanova made transition -
            Open Confirmed
            24m 19s 1
            Andrei Elkin made transition -
            Confirmed In Progress
            33d 11h 45m 1
            Andrei Elkin made transition -
            In Progress In Review
            2d 7h 5m 1
            Alexander Barkov made transition -
            In Review Stalled
            6d 22h 58m 1
            Andrei Elkin made transition -
            Stalled Closed
            4d 16h 33m 1

            People

              Elkin Andrei Elkin
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.