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

Wrong result (missing row) on a 2nd execution of PS with exists_to_in=on, MERGE view or a SELECT SQ

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.6
    • 10.0.11
    • None
    • None

    Description

      Test case:

      SET optimizer_switch='exists_to_in=on';
       
      CREATE TABLE t1 (a INT) ENGINE=MyISAM;
      INSERT INTO t1 VALUES (1),(2);
       
      CREATE ALGORITHM=MERGE VIEW v1 AS SELECT * FROM t1;
       
      CREATE TABLE t2 (b INT) ENGINE=MyISAM;
      INSERT INTO t2 VALUES (2),(3);
       
      SELECT * FROM v1 WHERE EXISTS ( SELECT * FROM t2 t2x, t2 t2y WHERE t2y.b = a );
       
      PREPARE stmt FROM "SELECT * FROM v1 WHERE EXISTS ( SELECT * FROM t2 t2x, t2 t2y WHERE t2y.b = a )";
      EXECUTE stmt;
      EXECUTE stmt;

      Results:

      MariaDB [test]> SELECT * FROM v1 WHERE EXISTS ( SELECT * FROM t2 t2x, t2 t2y WHERE t2y.b = a );
      +------+
      | a    |
      +------+
      |    2 |
      +------+
      1 row in set (0.01 sec)
       
      MariaDB [test]> PREPARE stmt FROM "SELECT * FROM v1 WHERE EXISTS ( SELECT * FROM t2 t2x, t2 t2y WHERE t2y.b = a );";
      Query OK, 0 rows affected (0.00 sec)
      Statement prepared
       
      MariaDB [test]> EXECUTE stmt;
      +------+
      | a    |
      +------+
      |    2 |
      +------+
      1 row in set (0.00 sec)
       
      MariaDB [test]> EXECUTE stmt;
      Empty set (0.00 sec)

      Also reproducible with a subquery instead of the view.

      Attachments

        Activity

          Materialization used to execute IN (got from exists).

          sanja Oleksandr Byelkin added a comment - Materialization used to execute IN (got from exists).

          It is correct explain:
          Note 1003 select `test`.`t1`.`a` AS `a` from `test`.`t1` semi join (`test`.`t2` `t2x` join `test`.`t2` `t2y`) where 1
          It is second execution one:
          Note 1003 select `test`.`t1`.`a` AS `a` from `test`.`t1` semi join (`test`.`t2` `t2x` join `test`.`t2` `t2y`) where ((`test`.`t1`.`a` = 1) and (`test`.`t2y`.`b` = 1))

          sanja Oleksandr Byelkin added a comment - It is correct explain: Note 1003 select `test`.`t1`.`a` AS `a` from `test`.`t1` semi join (`test`.`t2` `t2x` join `test`.`t2` `t2y`) where 1 It is second execution one: Note 1003 select `test`.`t1`.`a` AS `a` from `test`.`t1` semi join (`test`.`t2` `t2x` join `test`.`t2` `t2y`) where ((`test`.`t1`.`a` = 1) and (`test`.`t2y`.`b` = 1))

          The problem is in rolling back changes after we changed equations in WHERE with constants to remove it.

          ( (1=1) turns to (1=t1.a))

          sanja Oleksandr Byelkin added a comment - The problem is in rolling back changes after we changed equations in WHERE with constants to remove it. ( (1=1) turns to (1=t1.a))

          it is sent for review

          sanja Oleksandr Byelkin added a comment - it is sent for review

          People

            sanja Oleksandr Byelkin
            elenst Elena Stepanova
            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.