sl@0: # 2006 October 27
sl@0: #
sl@0: # The author disclaims copyright to this source code.  In place of
sl@0: # a legal notice, here is a blessing:
sl@0: #
sl@0: #    May you do good and not evil.
sl@0: #    May you find forgiveness for yourself and forgive others.
sl@0: #    May you share freely, never taking more than you give.
sl@0: #
sl@0: #***********************************************************************
sl@0: # This file implements regression tests for SQLite library.  The
sl@0: # focus of this file is testing the use of indices in WHERE clauses.
sl@0: # This file was created when support for optimizing IS NULL phrases
sl@0: # was added.  And so the principle purpose of this file is to test
sl@0: # that IS NULL phrases are correctly optimized.  But you can never
sl@0: # have too many tests, so some other tests are thrown in as well.
sl@0: #
sl@0: # $Id: where4.test,v 1.6 2007/12/10 05:03:48 danielk1977 Exp $
sl@0: 
sl@0: set testdir [file dirname $argv0]
sl@0: source $testdir/tester.tcl
sl@0: 
sl@0: ifcapable !tclvar||!bloblit {
sl@0:   finish_test
sl@0:   return
sl@0: }
sl@0: 
sl@0: # Build some test data
sl@0: #
sl@0: do_test where4-1.0 {
sl@0:   execsql {
sl@0:     CREATE TABLE t1(w, x, y);
sl@0:     CREATE INDEX i1wxy ON t1(w,x,y);
sl@0:     INSERT INTO t1 VALUES(1,2,3);
sl@0:     INSERT INTO t1 VALUES(1,NULL,3);
sl@0:     INSERT INTO t1 VALUES('a','b','c');
sl@0:     INSERT INTO t1 VALUES('a',NULL,'c');
sl@0:     INSERT INTO t1 VALUES(X'78',x'79',x'7a');
sl@0:     INSERT INTO t1 VALUES(X'78',NULL,X'7A');
sl@0:     INSERT INTO t1 VALUES(NULL,NULL,NULL);
sl@0:     SELECT count(*) FROM t1;
sl@0:   }
sl@0: } {7}
sl@0: 
sl@0: # Do an SQL statement.  Append the search count to the end of the result.
sl@0: #
sl@0: proc count sql {
sl@0:   set ::sqlite_search_count 0
sl@0:   return [concat [execsql $sql] $::sqlite_search_count]
sl@0: }
sl@0: 
sl@0: # Verify that queries use an index.  We are using the special variable
sl@0: # "sqlite_search_count" which tallys the number of executions of MoveTo
sl@0: # and Next operators in the VDBE.  By verifing that the search count is
sl@0: # small we can be assured that indices are being used properly.
sl@0: #
sl@0: do_test where4-1.1 {
sl@0:   count {SELECT rowid FROM t1 WHERE w IS NULL}
sl@0: } {7 2}
sl@0: do_test where4-1.2 {
sl@0:   count {SELECT rowid FROM t1 WHERE +w IS NULL}
sl@0: } {7 6}
sl@0: do_test where4-1.3 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=1 AND x IS NULL}
sl@0: } {2 2}
sl@0: do_test where4-1.4 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=1 AND +x IS NULL}
sl@0: } {2 3}
sl@0: do_test where4-1.5 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=1 AND x>0}
sl@0: } {1 2}
sl@0: do_test where4-1.6 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=1 AND x<9}
sl@0: } {1 3}
sl@0: do_test where4-1.7 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=1 AND x IS NULL AND y=3}
sl@0: } {2 2}
sl@0: do_test where4-1.8 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=1 AND x IS NULL AND y>2}
sl@0: } {2 2}
sl@0: do_test where4-1.9 {
sl@0:   count {SELECT rowid FROM t1 WHERE w='a' AND x IS NULL AND y='c'}
sl@0: } {4 2}
sl@0: do_test where4-1.10 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=x'78' AND x IS NULL}
sl@0: } {6 2}
sl@0: do_test where4-1.11 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=x'78' AND x IS NULL AND y=123}
sl@0: } {1}
sl@0: do_test where4-1.12 {
sl@0:   count {SELECT rowid FROM t1 WHERE w=x'78' AND x IS NULL AND y=x'7A'}
sl@0: } {6 2}
sl@0: do_test where4-1.13 {
sl@0:   count {SELECT rowid FROM t1 WHERE w IS NULL AND x IS NULL}
sl@0: } {7 2}
sl@0: do_test where4-1.14 {
sl@0:   count {SELECT rowid FROM t1 WHERE w IS NULL AND x IS NULL AND y IS NULL}
sl@0: } {7 2}
sl@0: do_test where4-1.15 {
sl@0:   count {SELECT rowid FROM t1 WHERE w IS NULL AND x IS NULL AND y<0}
sl@0: } {2}
sl@0: do_test where4-1.16 {
sl@0:   count {SELECT rowid FROM t1 WHERE w IS NULL AND x IS NULL AND y>=0}
sl@0: } {1}
sl@0: 
sl@0: do_test where4-2.1 {
sl@0:   execsql {SELECT rowid FROM t1 ORDER BY w, x, y}
sl@0: } {7 2 1 4 3 6 5}
sl@0: do_test where4-2.2 {
sl@0:   execsql {SELECT rowid FROM t1 ORDER BY w DESC, x, y}
sl@0: } {6 5 4 3 2 1 7}
sl@0: do_test where4-2.3 {
sl@0:   execsql {SELECT rowid FROM t1 ORDER BY w, x DESC, y}
sl@0: } {7 1 2 3 4 5 6}
sl@0: 
sl@0: 
sl@0: # Ticket #2177
sl@0: #
sl@0: # Suppose you have a left join where the right table of the left
sl@0: # join (the one that can be NULL) has an index on two columns.
sl@0: # The first indexed column is used in the ON clause of the join.
sl@0: # The second indexed column is used in the WHERE clause with an IS NULL
sl@0: # constraint.  It is not allowed to use the IS NULL optimization to
sl@0: # optimize the query because the second column might be NULL because
sl@0: # the right table did not match - something the index does not know
sl@0: # about.
sl@0: #
sl@0: do_test where4-3.1 {
sl@0:   execsql {
sl@0:     CREATE TABLE t2(a);
sl@0:     INSERT INTO t2 VALUES(1);
sl@0:     INSERT INTO t2 VALUES(2);
sl@0:     INSERT INTO t2 VALUES(3);
sl@0:     CREATE TABLE t3(x,y,UNIQUE(x,y));
sl@0:     INSERT INTO t3 VALUES(1,11);
sl@0:     INSERT INTO t3 VALUES(2,NULL);
sl@0:  
sl@0:     SELECT * FROM t2 LEFT JOIN t3 ON a=x WHERE +y IS NULL;
sl@0:   }
sl@0: } {2 2 {} 3 {} {}}
sl@0: do_test where4-3.2 {
sl@0:   execsql {
sl@0:     SELECT * FROM t2 LEFT JOIN t3 ON a=x WHERE y IS NULL;
sl@0:   }
sl@0: } {2 2 {} 3 {} {}}
sl@0: 
sl@0: # Ticket #2189.  Probably the same bug as #2177.
sl@0: #
sl@0: do_test where4-4.1 {
sl@0:   execsql {
sl@0:     CREATE TABLE test(col1 TEXT PRIMARY KEY);
sl@0:     INSERT INTO test(col1) values('a');
sl@0:     INSERT INTO test(col1) values('b');
sl@0:     INSERT INTO test(col1) values('c');
sl@0:     CREATE TABLE test2(col1 TEXT PRIMARY KEY);
sl@0:     INSERT INTO test2(col1) values('a');
sl@0:     INSERT INTO test2(col1) values('b');
sl@0:     INSERT INTO test2(col1) values('c');
sl@0:     SELECT * FROM test t1 LEFT OUTER JOIN test2 t2 ON t1.col1 = t2.col1
sl@0:       WHERE +t2.col1 IS NULL;
sl@0:   }
sl@0: } {}
sl@0: do_test where4-4.2 {
sl@0:   execsql {
sl@0:     SELECT * FROM test t1 LEFT OUTER JOIN test2 t2 ON t1.col1 = t2.col1
sl@0:       WHERE t2.col1 IS NULL;
sl@0:   }
sl@0: } {}
sl@0: do_test where4-4.3 {
sl@0:   execsql {
sl@0:     SELECT * FROM test t1 LEFT OUTER JOIN test2 t2 ON t1.col1 = t2.col1
sl@0:       WHERE +t1.col1 IS NULL;
sl@0:   }
sl@0: } {}
sl@0: do_test where4-4.4 {
sl@0:   execsql {
sl@0:     SELECT * FROM test t1 LEFT OUTER JOIN test2 t2 ON t1.col1 = t2.col1
sl@0:       WHERE t1.col1 IS NULL;
sl@0:   }
sl@0: } {}
sl@0: 
sl@0: # Ticket #2273.  Problems with IN operators and NULLs.
sl@0: #
sl@0: ifcapable subquery {
sl@0: do_test where4-5.1 {
sl@0:   execsql {
sl@0:     CREATE TABLE t4(x,y,z,PRIMARY KEY(x,y));
sl@0:   }
sl@0:   execsql {
sl@0:     SELECT *
sl@0:       FROM t2 LEFT JOIN t4 b1
sl@0:               LEFT JOIN t4 b2 ON b2.x=b1.x AND b2.y IN (b1.y);
sl@0:   }
sl@0: } {1 {} {} {} {} {} {} 2 {} {} {} {} {} {} 3 {} {} {} {} {} {}}
sl@0: do_test where4-5.2 {
sl@0:   execsql {
sl@0:     INSERT INTO t4 VALUES(1,1,11);
sl@0:     INSERT INTO t4 VALUES(1,2,12);
sl@0:     INSERT INTO t4 VALUES(1,3,13);
sl@0:     INSERT INTO t4 VALUES(2,2,22);
sl@0:     SELECT rowid FROM t4 WHERE x IN (1,9,2,5) AND y IN (1,3,NULL,2) AND z!=13;
sl@0:   }
sl@0: } {1 2 4}
sl@0: do_test where4-5.3 {
sl@0:   execsql {
sl@0:     SELECT rowid FROM t4 WHERE x IN (1,9,NULL,2) AND y IN (1,3,2) AND z!=13;
sl@0:   }
sl@0: } {1 2 4}
sl@0: do_test where4-6.1 {
sl@0:   execsql {
sl@0:     CREATE TABLE t5(a,b,c,d,e,f,UNIQUE(a,b,c,d,e,f));
sl@0:     INSERT INTO t5 VALUES(1,1,1,1,1,11111);
sl@0:     INSERT INTO t5 VALUES(2,2,2,2,2,22222);
sl@0:     INSERT INTO t5 VALUES(1,2,3,4,5,12345);
sl@0:     INSERT INTO t5 VALUES(2,3,4,5,6,23456);
sl@0:   }
sl@0:   execsql {
sl@0:     SELECT rowid FROM t5
sl@0:      WHERE a IN (1,9,2) AND b=2 AND c IN (1,2,3,4) AND d>0
sl@0:   }
sl@0: } {3 2}
sl@0: do_test where4-6.2 {
sl@0:   execsql {
sl@0:     SELECT rowid FROM t5
sl@0:      WHERE a IN (1,NULL,2) AND b=2 AND c IN (1,2,3,4) AND d>0
sl@0:   }
sl@0: } {3 2}
sl@0: do_test where4-7.1 {
sl@0:   execsql {
sl@0:     CREATE TABLE t6(y,z,PRIMARY KEY(y,z));
sl@0:   }
sl@0:   execsql {
sl@0:     SELECT * FROM t6 WHERE y=NULL AND z IN ('hello');
sl@0:   }
sl@0: } {}
sl@0: 
sl@0: integrity_check {where4-99.0}
sl@0: 
sl@0: do_test where4-7.1 {
sl@0:   execsql {
sl@0:     BEGIN;
sl@0:     CREATE TABLE t8(a, b, c, d);
sl@0:     CREATE INDEX t8_i ON t8(a, b, c);
sl@0:     CREATE TABLE t7(i);
sl@0: 
sl@0:     INSERT INTO t7 VALUES(1);
sl@0:     INSERT INTO t7 SELECT i*2 FROM t7;
sl@0:     INSERT INTO t7 SELECT i*2 FROM t7;
sl@0:     INSERT INTO t7 SELECT i*2 FROM t7;
sl@0:     INSERT INTO t7 SELECT i*2 FROM t7;
sl@0:     INSERT INTO t7 SELECT i*2 FROM t7;
sl@0:     INSERT INTO t7 SELECT i*2 FROM t7;
sl@0: 
sl@0:     COMMIT;
sl@0:   }
sl@0: } {}
sl@0: 
sl@0: # At one point the sub-select inside the aggregate sum() function in the
sl@0: # following query was leaking a couple of stack entries. This query 
sl@0: # runs the SELECT in a loop enough times that an assert() fails. Or rather,
sl@0: # did fail before the bug was fixed.
sl@0: #
sl@0: do_test where4-7.2 {
sl@0:   execsql {
sl@0:     SELECT sum((
sl@0:       SELECT d FROM t8 WHERE a = i AND b = i AND c < NULL
sl@0:     )) FROM t7;
sl@0:   }
sl@0: } {{}}
sl@0: 
sl@0: }; #ifcapable subquery
sl@0: 
sl@0: finish_test