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

CHAR(negativeWideDecimal) not behaving as InnoDB

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 6.1.1
    • 6.1.1
    • PrimProc
    • None
    • 2021-5

    Description

      DROP TABLE IF EXISTS t1;
      CREATE TABLE t1 (a DECIMAL(30,0)) ENGINE=ColumnStore;
      INSERT INTO t1 VALUES (-1);
      SELECT HEX(CHAR(a USING latin1)) FROM t1;
      

      +---------------------------+
      | HEX(CHAR(a USING latin1)) |
      +---------------------------+
      | NULL                      |
      +---------------------------+
      

      Looks wrong. The expected result is:

      DROP TABLE IF EXISTS t1;
      CREATE TABLE t1 (a DECIMAL(30,0)) ENGINE=InnoDB;
      INSERT INTO t1 VALUES (-1);
      SELECT HEX(CHAR(a USING latin1)) FROM t1;
      

      +---------------------------+
      | HEX(CHAR(a USING latin1)) |
      +---------------------------+
      | FFFFFFFF                  |
      +---------------------------+
      

      Note, negative narrow decimals do not have this problem and work as expected:

      DROP TABLE IF EXISTS t1;
      CREATE TABLE t1 (a DECIMAL(10,0)) ENGINE=ColumnStore;
      INSERT INTO t1 VALUES (-1);
      SELECT HEX(CHAR(a USING latin1)) FROM t1;
      

      +---------------------------+
      | HEX(CHAR(a USING latin1)) |
      +---------------------------+
      | FFFFFFFF                  |
      +---------------------------+
      

      Attachments

        Issue Links

          Activity

            People

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