Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 11.0.3
    • 11.2(EOL)
    • Optimizer
    • None
    • Ubuntu 22.04LTS

    Description

      The following two cases return different results for the same query.
      I construct case 2 by adding a not null constraint on case 1, which is expected to not change the query result.

      Case 1:

      DROP TABLE IF EXISTS t1;
      CREATE TABLE t1 (c0 double, c2 tinyint(1)) ENGINE=MyISAM;
      INSERT INTO t1 VALUES (-1, null);
      SELECT 1 HAVING ((1, NULL) NOT IN (SELECT `c2`, `c0` FROM t1)); -- {}
      

      Case 2:

      DROP TABLE IF EXISTS t1;
      CREATE TABLE t1 (c0 double not null , c2 tinyint(1)) ENGINE=MyISAM;
      INSERT INTO t1 VALUES (-1, null);
      SELECT 1 HAVING ((1, NULL) NOT IN (SELECT `c2`, `c0` FROM t1)); -- {1}
      

      Attachments

        Activity

          There are no comments yet on this issue.

          People

            psergei Sergei Petrunia
            John Jove John Jove
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.