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

COALESCE(12345678900) makes a column of a wrong type and truncates the data

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1(EOL), 10.2(EOL)
    • 10.3.1
    • OTHER
    • None

    Description

      DROP TABLE IF EXISTS t1;
      		 
      CREATE TABLE t1 AS SELECT 12345678900 AS c1, COALESCE(12345678900) AS c2;
      		 
      SELECT * FROM t1;
      		 
      SHOW CREATE TABLE t1;


      +-------------+------------+
      		 
      | c1          | c2         |
      		 
      +-------------+------------+
      		 
      | 12345678900 | 2147483647 |
      		 
      +-------------+------------+


      +-------+----------------------------------------------------------------------------------------------------------------+
      		 
      | Table | Create Table                                                                                                   |
      		 
      +-------+----------------------------------------------------------------------------------------------------------------+
      		 
      | t1    | CREATE TABLE `t1` (
      		 
        `c1` bigint(11) NOT NULL,
      		 
        `c2` int(11) NOT NULL
      		 
      ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
      		 
      +-------+---------------------------------------------------------------------------------------------------------------

      The expected result to create a BIGINT column for both expressions, and return 12345678900 for both columns.

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-4912 Data type plugin API version 1

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-10317 EXCTACT(MINUTE_MICROSECOND) truncates data

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MCOL-80 EXTRACT() function returned assertion error

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

          Activity

            Ascending order - Click to sort in descending order
            bar Alexander Barkov created issue -
            bar Alexander Barkov made changes -
            Field Original Value New Value
            Description {code:sql}
            DROP TABLE IF EXISTS t1;
            CREATE TABLE t1 AS SELECT 12345678900 AS c1, COALESCE(12345678900) AS c2;
            SELECT * FROM t1;
            SHOW CREATE TABLE t1;
            {code}

            {noformat}
            +-------------+------------+
            | c1 | c2 |
            +-------------+------------+
            | 12345678900 | 2147483647 |
            +-------------+------------+
            {noformat}

            {noformat}
            +-------+----------------------------------------------------------------------------------------------------------------+
            | Table | Create Table |
            +-------+----------------------------------------------------------------------------------------------------------------+
            | t1 | CREATE TABLE `t1` (
              `c1` bigint(11) NOT NULL,
              `c2` int(11) NOT NULL
            ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
            +-------+---------------------------------------------------------------------------------------------------------------
            {noformat}

            The expected result to to create a BIGINT column for both expressions.
            		{code:sql}
            DROP TABLE IF EXISTS t1;
            CREATE TABLE t1 AS SELECT 12345678900 AS c1, COALESCE(12345678900) AS c2;
            SELECT * FROM t1;
            SHOW CREATE TABLE t1;
            {code}

            {noformat}
            +-------------+------------+
            | c1 | c2 |
            +-------------+------------+
            | 12345678900 | 2147483647 |
            +-------------+------------+
            {noformat}

            {noformat}
            +-------+----------------------------------------------------------------------------------------------------------------+
            | Table | Create Table |
            +-------+----------------------------------------------------------------------------------------------------------------+
            | t1 | CREATE TABLE `t1` (
              `c1` bigint(11) NOT NULL,
              `c2` int(11) NOT NULL
            ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
            +-------+---------------------------------------------------------------------------------------------------------------
            {noformat}

            The expected result to create a BIGINT column for both expressions, and return 12345678900 for both columns.
            David.Hall David Hall (Inactive) made changes -
            bar Alexander Barkov added a comment -

            The same problem is repeatable with smaller numbers:

            CREATE OR REPLACE TABLE t1 AS SELECT 2147483648 AS c1, COALESCE(2147483648) AS c2;
            		 
            SHOW CREATE TABLE t1;
            		 
            SELECT * FROM t1;


            +-------+----------------------------------------------------------------------------------------------------------------+
            		 
            | Table | Create Table                                                                                                   |
            		 
            +-------+----------------------------------------------------------------------------------------------------------------+
            		 
            | t1    | CREATE TABLE `t1` (
            		 
              `c1` bigint(10) NOT NULL,
            		 
              `c2` int(10) NOT NULL
            		 
            ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
            		 
            +-------+----------------------------------------------------------------------------------------------------------------+


            +------------+------------+
            		 
            | c1         | c2         |
            		 
            +------------+------------+
            		 
            | 2147483648 | 2147483647 |
            		 
            +------------+------------+

            Notice, the data type and the value for c2 is wrong.

            bar Alexander Barkov added a comment - The same problem is repeatable with smaller numbers: CREATE OR REPLACE TABLE t1 AS SELECT 2147483648 AS c1, COALESCE (2147483648) AS c2; SHOW CREATE TABLE t1; SELECT * FROM t1; +-------+----------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +-------+----------------------------------------------------------------------------------------------------------------+ | t1 | CREATE TABLE `t1` ( `c1` bigint(10) NOT NULL, `c2` int(10) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1 | +-------+----------------------------------------------------------------------------------------------------------------+ +------------+------------+ | c1 | c2 | +------------+------------+ | 2147483648 | 2147483647 | +------------+------------+ Notice, the data type and the value for c2 is wrong.
            bar Alexander Barkov made changes -
            bar Alexander Barkov made changes -
            bar Alexander Barkov added a comment -

            Previous fixes in Type_handler
            (see the patch for MDEV-12875, MDEV-12886, MDEV-12916)
            fixed this problem as well. Adding only the test from the report.

            Pushed into bb-10.2-ext.

            bar Alexander Barkov added a comment - Previous fixes in Type_handler (see the patch for MDEV-12875 , MDEV-12886 , MDEV-12916 ) fixed this problem as well. Adding only the test from the report. Pushed into bb-10.2-ext.
            bar Alexander Barkov made changes -
            issue.field.resolutiondate 2017-05-27 12:08:57.0 2017-05-27 12:08:57.642
            bar Alexander Barkov made changes -
            Fix Version/s 10.3.1 [ 22532 ]
            Fix Version/s 10.1 [ 16100 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 76278 ] MariaDB v4 [ 150567 ]

            People

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