Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5035

MariaDB Columnstore all versions: update and inserts behave differently on 0000-00-00 00:00:00 datetime

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Icebox
    • Component/s: None
    • Labels:
    • Environment:
      Tested on 2 Systems:
      1.) MariaDB 10.5.13 RHEL 8.5
      2.) MariaDB 10.3.16 CentOS 7.6

      Description

      Both on EBI03 (MariaDB 10.5.13) and EBI01 (MariaDB 10.3.16) the following bug was found on Columnstore tables:

      an insert into a datetime field of '0000-00-00 00:00:00' stores it this way,
      BUT an UPDATE on datetime field of '0000-00-00 00:00:00' stores it as <null>

      whereas on InnoDB tables in both cases '0000-00-00 00:00:00' is stored.

      See the attached SQL.

      Note: the SQL_MODE options STRICT_TRANS_TABLES, ALLOW_INVALID_DATES, NO_ZERO_DATE, NO_ZERO_IN_DATE might have an impact.
      However, on the same session with the same set of SQL_MODE settings, in any case both engines should behave the same.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              aeae81 andreas eschbacher
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

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