3 # The author disclaims copyright to this source code. In place of
4 # a legal notice, here is a blessing:
6 # May you do good and not evil.
7 # May you find forgiveness for yourself and forgive others.
8 # May you share freely, never taking more than you give.
10 #*************************************************************************
11 # This file implements regression tests for SQLite library. The
12 # focus of this script is testing correlated subqueries
14 # $Id: subquery.test,v 1.9 2005/05/23 15:06:39 drh Exp $
17 set testdir [file dirname $argv0]
18 source $testdir/tester.tcl
25 do_test subquery-1.1 {
29 INSERT INTO t1 VALUES(1,2);
30 INSERT INTO t1 VALUES(3,4);
31 INSERT INTO t1 VALUES(5,6);
32 INSERT INTO t1 VALUES(7,8);
34 INSERT INTO t2 VALUES(1,1);
35 INSERT INTO t2 VALUES(3,9);
36 INSERT INTO t2 VALUES(5,25);
37 INSERT INTO t2 VALUES(7,49);
41 SELECT a, (SELECT y FROM t2 WHERE x=a) FROM t1 WHERE b<8
44 do_test subquery-1.2 {
46 UPDATE t1 SET b=b+(SELECT y FROM t2 WHERE x=a);
49 } {1 3 3 13 5 31 7 57}
51 do_test subquery-1.3 {
53 SELECT b FROM t1 WHERE EXISTS(SELECT * FROM t2 WHERE y=a)
56 do_test subquery-1.4 {
58 SELECT b FROM t1 WHERE NOT EXISTS(SELECT * FROM t2 WHERE y=a)
62 # Simple tests to make sure correlated subqueries in WHERE clauses
63 # are used by the query optimizer correctly.
64 do_test subquery-1.5 {
66 SELECT a, x FROM t1, t2 WHERE t1.a = (SELECT x);
69 do_test subquery-1.6 {
71 CREATE INDEX i1 ON t1(a);
72 SELECT a, x FROM t1, t2 WHERE t1.a = (SELECT x);
75 do_test subquery-1.7 {
77 SELECT a, x FROM t2, t1 WHERE t1.a = (SELECT x);
81 # Try an aggregate in both the subquery and the parent query.
82 do_test subquery-1.8 {
84 SELECT count(*) FROM t1 WHERE a > (SELECT count(*) FROM t2);
88 # Test a correlated subquery disables the "only open the index" optimization.
89 do_test subquery-1.9.1 {
91 SELECT (y*2)>b FROM t1, t2 WHERE a=x;
94 do_test subquery-1.9.2 {
96 SELECT a FROM t1 WHERE (SELECT (y*2)>b FROM t2 WHERE a=x);
100 # Test that the flattening optimization works with subquery expressions.
101 do_test subquery-1.10.1 {
103 SELECT (SELECT a), b FROM t1;
105 } {1 3 3 13 5 31 7 57}
106 do_test subquery-1.10.2 {
108 SELECT * FROM (SELECT (SELECT a), b FROM t1);
110 } {1 3 3 13 5 31 7 57}
111 do_test subquery-1.10.3 {
113 SELECT * FROM (SELECT (SELECT sum(a) FROM t1));
116 do_test subquery-1.10.4 {
118 CREATE TABLE t5 (val int, period text PRIMARY KEY);
119 INSERT INTO t5 VALUES(5, '2001-3');
120 INSERT INTO t5 VALUES(10, '2001-4');
121 INSERT INTO t5 VALUES(15, '2002-1');
122 INSERT INTO t5 VALUES(5, '2002-2');
123 INSERT INTO t5 VALUES(10, '2002-3');
124 INSERT INTO t5 VALUES(15, '2002-4');
125 INSERT INTO t5 VALUES(10, '2003-1');
126 INSERT INTO t5 VALUES(5, '2003-2');
127 INSERT INTO t5 VALUES(25, '2003-3');
128 INSERT INTO t5 VALUES(5, '2003-4');
130 SELECT "a.period", vsum
133 (select sum(val) from t5 where period between a.period and '2002-4') vsum
134 FROM t5 a where a.period between '2002-1' and '2002-4')
137 } {2002-2 30.0 2002-3 25.0 2002-4 15.0}
138 do_test subquery-1.10.5 {
140 SELECT "a.period", vsum from
142 (select sum(val) from t5 where period between a.period and '2002-4') vsum
143 FROM t5 a where a.period between '2002-1' and '2002-4')
146 } {2002-2 30.0 2002-3 25.0 2002-4 15.0}
147 do_test subquery-1.10.6 {
155 #------------------------------------------------------------------
156 # The following test cases - subquery-2.* - are not logically
157 # organized. They're here largely because they were failing during
158 # one stage of development of sub-queries.
160 do_test subquery-2.1 {
165 do_test subquery-2.2.1 {
167 CREATE TABLE t3(a PRIMARY KEY, b);
168 INSERT INTO t3 VALUES(1, 2);
169 INSERT INTO t3 VALUES(3, 1);
172 do_test subquery-2.2.2 {
174 SELECT * FROM t3 WHERE a IN (SELECT b FROM t3);
177 do_test subquery-2.2.3 {
182 do_test subquery-2.3.1 {
184 CREATE TABLE t3(a TEXT);
185 INSERT INTO t3 VALUES('10');
188 do_test subquery-2.3.2 {
190 SELECT a IN (10.0, 20) FROM t3;
193 do_test subquery-2.3.3 {
198 do_test subquery-2.4.1 {
200 CREATE TABLE t3(a TEXT);
201 INSERT INTO t3 VALUES('XX');
204 do_test subquery-2.4.2 {
206 SELECT count(*) FROM t3 WHERE a IN (SELECT 'XX')
209 do_test subquery-2.4.3 {
214 do_test subquery-2.5.1 {
216 CREATE TABLE t3(a INTEGER);
217 INSERT INTO t3 VALUES(10);
219 CREATE TABLE t4(x TEXT);
220 INSERT INTO t4 VALUES('10.0');
223 do_test subquery-2.5.2 {
225 SELECT * FROM t4 WHERE x IN (SELECT a FROM t3);
228 do_test subquery-2.5.3 {
230 CREATE INDEX t4i ON t4(x);
231 SELECT * FROM t4 WHERE x IN (SELECT a FROM t3);
234 do_test subquery-2.5.4 {
241 #------------------------------------------------------------------
242 # The following test cases - subquery-3.* - test tickets that
243 # were raised during development of correlated subqueries.
248 do_test subquery-3.1 {
249 catchsql { DROP TABLE t1; }
250 catchsql { DROP TABLE t2; }
252 CREATE TABLE t1(a,b);
253 INSERT INTO t1 VALUES(1,2);
254 CREATE VIEW v1 AS SELECT b FROM t1 WHERE a>0;
255 CREATE TABLE t2(p,q);
256 INSERT INTO t2 VALUES(2,9);
257 SELECT * FROM v1 WHERE EXISTS(SELECT * FROM t2 WHERE p=v1.b);
263 do_test subquery-3.2 {
265 CREATE TABLE t1(a,b);
266 INSERT INTO t1 VALUES(1,2);
269 SELECT (SELECT t1.a) FROM t1;
273 # Test Cases subquery-3.3.* test correlated subqueries where the
274 # parent query is an aggregate query. Ticket #1105 is an example
277 do_test subquery-3.3.1 {
279 SELECT a, (SELECT b) FROM t1 GROUP BY a;
282 do_test subquery-3.3.2 {
283 catchsql {DROP TABLE t2}
285 CREATE TABLE t2(c, d);
286 INSERT INTO t2 VALUES(1, 'one');
287 INSERT INTO t2 VALUES(2, 'two');
288 SELECT a, (SELECT d FROM t2 WHERE a=c) FROM t1 GROUP BY a;
291 do_test subquery-3.3.3 {
293 INSERT INTO t1 VALUES(2, 4);
294 SELECT max(a), (SELECT d FROM t2 WHERE a=c) FROM t1;
297 do_test subquery-3.3.4 {
299 SELECT a, (SELECT (SELECT d FROM t2 WHERE a=c)) FROM t1 GROUP BY a;
302 do_test subquery-3.3.5 {
304 SELECT a, (SELECT count(*) FROM t2 WHERE a=c) FROM t1;
308 #------------------------------------------------------------------
309 # These tests - subquery-4.* - use the TCL statement cache to try
310 # and expose bugs to do with re-using statements that have been
311 # passed to sqlite3_reset().
313 # One problem was that VDBE memory cells were not being initialised
314 # to NULL on the second and subsequent executions.
316 do_test subquery-4.1.1 {
318 SELECT (SELECT a FROM t1);
321 do_test subquery-4.2 {
324 SELECT (SELECT a FROM t1);
327 do_test subquery-4.2.1 {
329 CREATE TABLE t3(a PRIMARY KEY);
330 INSERT INTO t3 VALUES(10);
332 execsql {INSERT INTO t3 VALUES((SELECT max(a) FROM t3)+1)}
334 do_test subquery-4.2.2 {
335 execsql {INSERT INTO t3 VALUES((SELECT max(a) FROM t3)+1)}
338 #------------------------------------------------------------------
339 # The subquery-5.* tests make sure string literals in double-quotes
340 # are handled efficiently. Double-quote literals are first checked
341 # to see if they match any column names. If there is not column name
342 # match then those literals are used a string constants. When a
343 # double-quoted string appears, we want to make sure that the search
344 # for a matching column name did not cause an otherwise static subquery
345 # to become a dynamic (correlated) subquery.
347 do_test subquery-5.1 {
348 proc callcntproc {n} {
353 db function callcnt callcntproc
355 CREATE TABLE t4(x,y);
356 INSERT INTO t4 VALUES('one',1);
357 INSERT INTO t4 VALUES('two',2);
358 INSERT INTO t4 VALUES('three',3);
359 INSERT INTO t4 VALUES('four',4);
360 CREATE TABLE t5(a,b);
361 INSERT INTO t5 VALUES(1,11);
362 INSERT INTO t5 VALUES(2,22);
363 INSERT INTO t5 VALUES(3,33);
364 INSERT INTO t5 VALUES(4,44);
365 SELECT b FROM t5 WHERE a IN
366 (SELECT callcnt(y)+0 FROM t4 WHERE x="two")
369 do_test subquery-5.2 {
370 # This is the key test. The subquery should have only run once. If
371 # The double-quoted identifier "two" were causing the subquery to be
372 # processed as a correlated subquery, then it would have run 4 times.