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

Dependent query cannot recognize expr in more than 1 nesting level

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.5, 10.6, 10.9(EOL)
    • N/A
    • OTHER
    • None

    Description

      repro: https://dbfiddle.uk/1BpvGW2V

      here is the same repro working for MySQL: https://dbfiddle.uk/wa8Kc48N
      and for PostgreSQL: https://dbfiddle.uk/6Z-IfLMx

      The failing query patten is important to be supported. In complex queries, it allows to deduplicate subqueries used later more than one without having to put them in the main select.

      I would be grateful if it can be fixed.

      Attachments

        Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. MDEV-19078 Support lateral derived tables

          • Major - Major loss of function.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            mv Michael created issue -
            mv Michael made changes -
            Field Original Value New Value
            Description repro: https://dbfiddle.uk/1BpvGW2V

            here is the same repro working for MySQL: dbfiddle.uk/wa8Kc48N
            and for PostgreSQL: dbfiddle.uk/6Z-IfLMx

            The failing query patten is important to be supported. In complex queries, it allows to deduplicate subqueries used later more than one without having to put them in the main select.

            I would be grateful if it can be fixed.             		repro: https://dbfiddle.uk/1BpvGW2V

            here is the same repro working for MySQL: https://dbfiddle.uk/wa8Kc48N
            and for PostgreSQL: https://dbfiddle.uk/6Z-IfLMx

            The failing query patten is important to be supported. In complex queries, it allows to deduplicate subqueries used later more than one without having to put them in the main select.

            I would be grateful if it can be fixed.
            mv Michael made changes -
            Summary Dependent query cannot recognize aggregate expr in more than 1 nesting level Dependent query cannot recognize expr in more than 1 nesting level
            serg Sergei Golubchik made changes -
            Affects Version/s 10.9 [ 26905 ]
            serg Sergei Golubchik made changes -
            Affects Version/s 10.5 [ 23123 ]
            Affects Version/s 10.6 [ 24028 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.11 [ 27614 ]
            Fix Version/s 11.0 [ 28320 ]
            Fix Version/s 11.1 [ 28549 ]
            Fix Version/s 11.2 [ 28603 ]
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            serg Sergei Golubchik made changes -
            Assignee Oleksandr Byelkin [ sanja ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 11.0 [ 28320 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 11.1 [ 28549 ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 11.2(EOL) [ 28603 ]
            sanja Oleksandr Byelkin made changes -
            issue.field.resolutiondate 2024-11-26 09:43:28.0 2024-11-26 09:43:28.163
            sanja Oleksandr Byelkin made changes -
            Component/s OTHER [ 10125 ]
            Fix Version/s N/A [ 14700 ]
            Fix Version/s 10.11 [ 27614 ]
            Resolution Not a Bug [ 6 ]
            Status Confirmed [ 10101 ] Closed [ 6 ]
            sanja Oleksandr Byelkin made changes -

            People

              sanja Oleksandr Byelkin
              mv Michael
              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.