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

Remove parser tokens DECODE_MARIADB_SYM and DECODE_ORACLE_SYM

Details

    Description

      In order to fix MDEV-27744 easier, let's change the code handling sql_mode-dependent function DECODE(), as the follows:

      • remove parser tokens DECODE_MARIADB_SYM and DECODE_ORACLE_SYM handling sql_mode-dependent function DECODE()
      • remove the DECODE() code from sql_yacc.yy/sql_yacc_ora.yy
      • add handling of DECODE() using regular Create_func means

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27744 LPAD in vcol created in ORACLE mode makes table corrupted in non-ORACLE

          • Critical - Crashes, loss of data, severe memory leak.
          • 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
            bar Alexander Barkov made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            julien.fritsch Julien Fritsch made changes -
            Assignee Alexander Barkov [ bar ]
            bar Alexander Barkov made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            bar Alexander Barkov made changes -
            Assignee Alexander Barkov [ bar ] Sergei Golubchik [ serg ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            bar Alexander Barkov made changes -
            bar Alexander Barkov made changes -
            bar Alexander Barkov added a comment -

            Hello Sergei Golubchik, please find the latest patch here:

            https://github.com/MariaDB/server/commits/bb-10.4-bar-MDEV-27744-v2

            There are three patches in this branch:
            MDEV-31184
            MDEV-31187
            MDEV-27744

            Thanks.

            bar Alexander Barkov added a comment - Hello Sergei Golubchik, please find the latest patch here: https://github.com/MariaDB/server/commits/bb-10.4-bar-MDEV-27744-v2 There are three patches in this branch: MDEV-31184 MDEV-31187 MDEV-27744 Thanks.
            bar Alexander Barkov added a comment -

            serg, please find a new patch version here:

            https://github.com/MariaDB/server/commit/0e43e544a8d03163ad0cbc8479d0ae3cf7b191e3

            bar Alexander Barkov added a comment - serg , please find a new patch version here: https://github.com/MariaDB/server/commit/0e43e544a8d03163ad0cbc8479d0ae3cf7b191e3
            serg Sergei Golubchik added a comment -

            0e43e544a8d is ok to push, thanks!

            serg Sergei Golubchik added a comment - 0e43e544a8d is ok to push, thanks!
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ] Alexander Barkov [ bar ]
            Status In Review [ 10002 ] Stalled [ 10000 ]
            bar Alexander Barkov made changes -
            Fix Version/s 10.4.32 [ 29300 ]
            Fix Version/s 10.5.23 [ 29012 ]
            Fix Version/s 10.6.16 [ 29014 ]
            Fix Version/s 10.10.7 [ 29018 ]
            Fix Version/s 10.11.6 [ 29020 ]
            Fix Version/s 11.0.4 [ 29021 ]
            Fix Version/s 11.1.3 [ 29023 ]
            Fix Version/s 11.2.2 [ 29035 ]
            Fix Version/s 11.3.1 [ 29416 ]
            Fix Version/s 10.9.8 [ 29015 ]
            Fix Version/s 10.8.8 [ 28518 ]
            Fix Version/s 10.4 [ 22408 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]

            People

              bar Alexander Barkov
              bar Alexander Barkov
              Votes:
              0 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.