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

Decimal precision

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.4.15
    • N/A
    • N/A
    • None
    • docker node:12-alpine

    Description

      I have the following query "SELECT 6/101*100"

      In mariadb-10.4.13 it returns "5.9406"
      In mariadb-10.4.15 it returns "5.9400"

      Attached the output of "SHOW VARIABLES"

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23702 calculating(auto rounding) issue

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            vadim_sirbu Vadim Sirbu created issue -
            alice Alice Sherepa made changes -
            Field Original Value New Value
            alice Alice Sherepa added a comment -

            Thanks! MDEV-23702 was reported for the same bug, If you'd like to follow the progress, please, watch task MDEV-23702.
            As a temporary workaround, one could change div_precision_increment:

            MariaDB [(none)]> SELECT 6/101*100;
            		 
            +-----------+
            		 
            | 6/101*100 |
            		 
            +-----------+
            		 
            |    5.9400 |
            		 
            +-----------+
            		 
            1 row in set (0.001 sec)
            		 
             
            		 
            MariaDB [(none)]> set div_precision_increment=8;
            		 
            Query OK, 0 rows affected (0.001 sec)
            		 
             
            		 
            MariaDB [(none)]> SELECT 6/101*100;
            		 
            +------------+
            		 
            | 6/101*100  |
            		 
            +------------+
            		 
            | 5.94059400 |
            		 
            +------------+
            		 
            1 row in set (0.000 sec)

            alice Alice Sherepa added a comment - Thanks! MDEV-23702 was reported for the same bug, If you'd like to follow the progress, please, watch task MDEV-23702 . As a temporary workaround, one could change div_precision_increment: MariaDB [(none)]> SELECT 6/101*100; +-----------+ | 6/101*100 | +-----------+ | 5.9400 | +-----------+ 1 row in set (0.001 sec)   MariaDB [(none)]> set div_precision_increment=8; Query OK, 0 rows affected (0.001 sec)   MariaDB [(none)]> SELECT 6/101*100; +------------+ | 6/101*100 | +------------+ | 5.94059400 | +------------+ 1 row in set (0.000 sec)
            alice Alice Sherepa made changes -
            Component/s N/A [ 14411 ]
            Fix Version/s N/A [ 14700 ]
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 114553 ] MariaDB v4 [ 158466 ]

            People

              Unassigned Unassigned
              vadim_sirbu Vadim Sirbu
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.