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

Server crashes in Item_field::fix_outer_field place= prev_subselect_item->parsing_place (prev_subselect_item=NULL)

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.4, 10.6.12, 10.5, 10.6, 10.9, 10.10, 10.11, 11.0, 10.5.22, 10.6.15
    • N/A
    • 10.6.12-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04

      and

      Ubuntu 19.10 / MariaDB-1:10.4.14

    Description

      CREATE OR REPLACE TEMPORARY TABLE a (
      	ID INT
      );
       
      CREATE OR REPLACE TEMPORARY TABLE b (
      	ID INT
      );
       
      CREATE OR REPLACE  TEMPORARY TABLE c (
      	ID INT
      );
       
      CREATE OR REPLACE TEMPORARY TABLE d (
      	ID INT
      );
       
      -- Query A
      SELECT 'A'
      UNION
      SELECT 'B'
      UNION
      SELECT DISTINCT 1
      FROM a
      INNER JOIN b
      	on a.ID = b.ID AND EXISTS (SELECT * FROM d WHERE b.ID = c.ID )
      INNER JOIN c
      	on b.ID = c.ID;
       
      -- Query B
      SELECT DISTINCT 1
      FROM a
      INNER JOIN b
      	on a.ID = b.ID AND EXISTS (SELECT * FROM d WHERE b.ID = c.ID )
      INNER JOIN c
      	on b.ID = c.ID;
      

      On 10.4 :
      Query A and B : OK (no syntax error : Unknown column 'c.ID' in 'where clause')

      On 10.6 :
      Query B : KO syntax error : Unknown column 'c.ID' in 'where clause'

      Query A : KO Lost connection to server during query (and mariadb restart)

      Attachments

        Issue Links

          Activity

            People

              igor Igor Babaev
              yotheguitou Guillaume Girardi
              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.