mirrors/sqlite
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
529394e5c1
sqlite/test/where9.test
drh 93ffb50fcd In the MULTI-INDEX OR query plan, code for sub-expressions can sometimes be 
generated twice.  But for some subqueries, generating code off of the same
tree twice causes problems.  So now MULTI-INDEX OR makes a copy of the
sub-expressions it uses to avoid code-generating them more than once.
dbsqlfuzz 9ebd2140e7206ff724e665f172faea28af801635.

FossilOrigin-Name: 4a55f72542c8bcc80253aa77043314cecb29d73cb4f51aa80f7811e86cc8ef68
2021-05-18 19:10:10 +00:00

1005 lines
32 KiB
Plaintext
Raw Blame History

# 2008 December 30
#
# The author disclaims copyright to this source code. In place of
# a legal notice, here is a blessing:
#
# May you do good and not evil.
# May you find forgiveness for yourself and forgive others.
# May you share freely, never taking more than you give.
#
#***********************************************************************
# This file implements regression tests for SQLite library. The
# focus of this file is testing the multi-index OR clause optimizer.
#
set testdir [file dirname $argv0]
source $testdir/tester.tcl
ifcapable !or_opt||!compound {
finish_test
return
}
# Evaluate SQL. Return the result set followed by the
# and the number of full-scan steps.
#
proc count_steps {sql} {
set r [db eval $sql]
lappend r scan [db status step] sort [db status sort]
}
# Construct test data.
#
do_test where9-1.1 {
db eval {
CREATE TABLE t1(a INTEGER PRIMARY KEY,b,c,d,e,f,g);
INSERT INTO t1 VALUES(1,11,1001,1.001,100.1,'bcdefghij','yxwvuts');
INSERT INTO t1 VALUES(2,22,1001,2.002,100.1,'cdefghijk','yxwvuts');
INSERT INTO t1 VALUES(3,33,1001,3.003,100.1,'defghijkl','xwvutsr');
INSERT INTO t1 VALUES(4,44,2002,4.004,200.2,'efghijklm','xwvutsr');
INSERT INTO t1 VALUES(5,55,2002,5.005,200.2,'fghijklmn','xwvutsr');
INSERT INTO t1 VALUES(6,66,2002,6.006,200.2,'ghijklmno','xwvutsr');
INSERT INTO t1 VALUES(7,77,3003,7.007,300.3,'hijklmnop','xwvutsr');
INSERT INTO t1 VALUES(8,88,3003,8.008,300.3,'ijklmnopq','wvutsrq');
INSERT INTO t1 VALUES(9,99,3003,9.009,300.3,'jklmnopqr','wvutsrq');
INSERT INTO t1 VALUES(10,110,4004,10.01,400.4,'klmnopqrs','wvutsrq');
INSERT INTO t1 VALUES(11,121,4004,11.011,400.4,'lmnopqrst','wvutsrq');
INSERT INTO t1 VALUES(12,132,4004,12.012,400.4,'mnopqrstu','wvutsrq');
INSERT INTO t1 VALUES(13,143,5005,13.013,500.5,'nopqrstuv','vutsrqp');
INSERT INTO t1 VALUES(14,154,5005,14.014,500.5,'opqrstuvw','vutsrqp');
INSERT INTO t1 VALUES(15,165,5005,15.015,500.5,'pqrstuvwx','vutsrqp');
INSERT INTO t1 VALUES(16,176,6006,16.016,600.6,'qrstuvwxy','vutsrqp');
INSERT INTO t1 VALUES(17,187,6006,17.017,600.6,'rstuvwxyz','vutsrqp');
INSERT INTO t1 VALUES(18,198,6006,18.018,600.6,'stuvwxyza','utsrqpo');
INSERT INTO t1 VALUES(19,209,7007,19.019,700.7,'tuvwxyzab','utsrqpo');
INSERT INTO t1 VALUES(20,220,7007,20.02,700.7,'uvwxyzabc','utsrqpo');
INSERT INTO t1 VALUES(21,231,7007,21.021,700.7,'vwxyzabcd','utsrqpo');
INSERT INTO t1 VALUES(22,242,8008,22.022,800.8,'wxyzabcde','utsrqpo');
INSERT INTO t1 VALUES(23,253,8008,23.023,800.8,'xyzabcdef','tsrqpon');
INSERT INTO t1 VALUES(24,264,8008,24.024,800.8,'yzabcdefg','tsrqpon');
INSERT INTO t1 VALUES(25,275,9009,25.025,900.9,'zabcdefgh','tsrqpon');
INSERT INTO t1 VALUES(26,286,9009,26.026,900.9,'abcdefghi','tsrqpon');
INSERT INTO t1 VALUES(27,297,9009,27.027,900.9,'bcdefghij','tsrqpon');
INSERT INTO t1 VALUES(28,308,10010,28.028,1001.0,'cdefghijk','srqponm');
INSERT INTO t1 VALUES(29,319,10010,29.029,1001.0,'defghijkl','srqponm');
INSERT INTO t1 VALUES(30,330,10010,30.03,1001.0,'efghijklm','srqponm');
INSERT INTO t1 VALUES(31,341,11011,31.031,1101.1,'fghijklmn','srqponm');
INSERT INTO t1 VALUES(32,352,11011,32.032,1101.1,'ghijklmno','srqponm');
INSERT INTO t1 VALUES(33,363,11011,33.033,1101.1,'hijklmnop','rqponml');
INSERT INTO t1 VALUES(34,374,12012,34.034,1201.2,'ijklmnopq','rqponml');
INSERT INTO t1 VALUES(35,385,12012,35.035,1201.2,'jklmnopqr','rqponml');
INSERT INTO t1 VALUES(36,396,12012,36.036,1201.2,'klmnopqrs','rqponml');
INSERT INTO t1 VALUES(37,407,13013,37.037,1301.3,'lmnopqrst','rqponml');
INSERT INTO t1 VALUES(38,418,13013,38.038,1301.3,'mnopqrstu','qponmlk');
INSERT INTO t1 VALUES(39,429,13013,39.039,1301.3,'nopqrstuv','qponmlk');
INSERT INTO t1 VALUES(40,440,14014,40.04,1401.4,'opqrstuvw','qponmlk');
INSERT INTO t1 VALUES(41,451,14014,41.041,1401.4,'pqrstuvwx','qponmlk');
INSERT INTO t1 VALUES(42,462,14014,42.042,1401.4,'qrstuvwxy','qponmlk');
INSERT INTO t1 VALUES(43,473,15015,43.043,1501.5,'rstuvwxyz','ponmlkj');
INSERT INTO t1 VALUES(44,484,15015,44.044,1501.5,'stuvwxyza','ponmlkj');
INSERT INTO t1 VALUES(45,495,15015,45.045,1501.5,'tuvwxyzab','ponmlkj');
INSERT INTO t1 VALUES(46,506,16016,46.046,1601.6,'uvwxyzabc','ponmlkj');
INSERT INTO t1 VALUES(47,517,16016,47.047,1601.6,'vwxyzabcd','ponmlkj');
INSERT INTO t1 VALUES(48,528,16016,48.048,1601.6,'wxyzabcde','onmlkji');
INSERT INTO t1 VALUES(49,539,17017,49.049,1701.7,'xyzabcdef','onmlkji');
INSERT INTO t1 VALUES(50,550,17017,50.05,1701.7,'yzabcdefg','onmlkji');
INSERT INTO t1 VALUES(51,561,17017,51.051,1701.7,'zabcdefgh','onmlkji');
INSERT INTO t1 VALUES(52,572,18018,52.052,1801.8,'abcdefghi','onmlkji');
INSERT INTO t1 VALUES(53,583,18018,53.053,1801.8,'bcdefghij','nmlkjih');
INSERT INTO t1 VALUES(54,594,18018,54.054,1801.8,'cdefghijk','nmlkjih');
INSERT INTO t1 VALUES(55,605,19019,55.055,1901.9,'defghijkl','nmlkjih');
INSERT INTO t1 VALUES(56,616,19019,56.056,1901.9,'efghijklm','nmlkjih');
INSERT INTO t1 VALUES(57,627,19019,57.057,1901.9,'fghijklmn','nmlkjih');
INSERT INTO t1 VALUES(58,638,20020,58.058,2002.0,'ghijklmno','mlkjihg');
INSERT INTO t1 VALUES(59,649,20020,59.059,2002.0,'hijklmnop','mlkjihg');
INSERT INTO t1 VALUES(60,660,20020,60.06,2002.0,'ijklmnopq','mlkjihg');
INSERT INTO t1 VALUES(61,671,21021,61.061,2102.1,'jklmnopqr','mlkjihg');
INSERT INTO t1 VALUES(62,682,21021,62.062,2102.1,'klmnopqrs','mlkjihg');
INSERT INTO t1 VALUES(63,693,21021,63.063,2102.1,'lmnopqrst','lkjihgf');
INSERT INTO t1 VALUES(64,704,22022,64.064,2202.2,'mnopqrstu','lkjihgf');
INSERT INTO t1 VALUES(65,715,22022,65.065,2202.2,'nopqrstuv','lkjihgf');
INSERT INTO t1 VALUES(66,726,22022,66.066,2202.2,'opqrstuvw','lkjihgf');
INSERT INTO t1 VALUES(67,737,23023,67.067,2302.3,'pqrstuvwx','lkjihgf');
INSERT INTO t1 VALUES(68,748,23023,68.068,2302.3,'qrstuvwxy','kjihgfe');
INSERT INTO t1 VALUES(69,759,23023,69.069,2302.3,'rstuvwxyz','kjihgfe');
INSERT INTO t1 VALUES(70,770,24024,70.07,2402.4,'stuvwxyza','kjihgfe');
INSERT INTO t1 VALUES(71,781,24024,71.071,2402.4,'tuvwxyzab','kjihgfe');
INSERT INTO t1 VALUES(72,792,24024,72.072,2402.4,'uvwxyzabc','kjihgfe');
INSERT INTO t1 VALUES(73,803,25025,73.073,2502.5,'vwxyzabcd','jihgfed');
INSERT INTO t1 VALUES(74,814,25025,74.074,2502.5,'wxyzabcde','jihgfed');
INSERT INTO t1 VALUES(75,825,25025,75.075,2502.5,'xyzabcdef','jihgfed');
INSERT INTO t1 VALUES(76,836,26026,76.076,2602.6,'yzabcdefg','jihgfed');
INSERT INTO t1 VALUES(77,847,26026,77.077,2602.6,'zabcdefgh','jihgfed');
INSERT INTO t1 VALUES(78,858,26026,78.078,2602.6,'abcdefghi','ihgfedc');
INSERT INTO t1 VALUES(79,869,27027,79.079,2702.7,'bcdefghij','ihgfedc');
INSERT INTO t1 VALUES(80,880,27027,80.08,2702.7,'cdefghijk','ihgfedc');
INSERT INTO t1 VALUES(81,891,27027,81.081,2702.7,'defghijkl','ihgfedc');
INSERT INTO t1 VALUES(82,902,28028,82.082,2802.8,'efghijklm','ihgfedc');
INSERT INTO t1 VALUES(83,913,28028,83.083,2802.8,'fghijklmn','hgfedcb');
INSERT INTO t1 VALUES(84,924,28028,84.084,2802.8,'ghijklmno','hgfedcb');
INSERT INTO t1 VALUES(85,935,29029,85.085,2902.9,'hijklmnop','hgfedcb');
INSERT INTO t1 VALUES(86,946,29029,86.086,2902.9,'ijklmnopq','hgfedcb');
INSERT INTO t1 VALUES(87,957,29029,87.087,2902.9,'jklmnopqr','hgfedcb');
INSERT INTO t1 VALUES(88,968,30030,88.088,3003.0,'klmnopqrs','gfedcba');
INSERT INTO t1 VALUES(89,979,30030,89.089,3003.0,'lmnopqrst','gfedcba');
INSERT INTO t1 VALUES(90,NULL,30030,90.09,3003.0,'mnopqrstu','gfedcba');
INSERT INTO t1 VALUES(91,1001,NULL,91.091,3103.1,'nopqrstuv','gfedcba');
INSERT INTO t1 VALUES(92,1012,31031,NULL,3103.1,'opqrstuvw','gfedcba');
INSERT INTO t1 VALUES(93,1023,31031,93.093,NULL,'pqrstuvwx','fedcbaz');
INSERT INTO t1 VALUES(94,1034,32032,94.094,3203.2,NULL,'fedcbaz');
INSERT INTO t1 VALUES(95,1045,32032,95.095,3203.2,'rstuvwxyz',NULL);
INSERT INTO t1 VALUES(96,NULL,NULL,96.096,3203.2,'stuvwxyza','fedcbaz');
INSERT INTO t1 VALUES(97,1067,33033,NULL,NULL,'tuvwxyzab','fedcbaz');
INSERT INTO t1 VALUES(98,1078,33033,98.098,3303.3,NULL,NULL);
INSERT INTO t1 VALUES(99,NULL,NULL,NULL,NULL,NULL,NULL);
CREATE INDEX t1b ON t1(b);
CREATE INDEX t1c ON t1(c);
CREATE INDEX t1d ON t1(d);
CREATE INDEX t1e ON t1(e);
CREATE INDEX t1f ON t1(f);
CREATE INDEX t1g ON t1(g);
CREATE TABLE t2(a INTEGER PRIMARY KEY,b,c,d,e,f,g);
INSERT INTO t2 SELECT * FROM t1;
CREATE INDEX t2b ON t2(b,c);
CREATE INDEX t2c ON t2(c,e);
CREATE INDEX t2d ON t2(d,g);
CREATE INDEX t2e ON t2(e,f,g);
CREATE INDEX t2f ON t2(f,b,d,c);
CREATE INDEX t2g ON t2(g,f);
CREATE TABLE t3(x,y);
INSERT INTO t3 VALUES(1,80);
INSERT INTO t3 VALUES(2,80);
CREATE TABLE t4(a INTEGER PRIMARY KEY,b,c,d,e,f,g);
INSERT INTO t4 SELECT * FROM t1;
CREATE INDEX t4b ON t4(b);
CREATE INDEX t4c ON t4(c);
}
} {}
do_test where9-1.2.1 {
count_steps {
SELECT a FROM t1
WHERE b IS NULL
OR c IS NULL
OR d IS NULL
ORDER BY a
}
} {90 91 92 96 97 99 scan 0 sort 1}
do_test where9-1.2.2 {
count_steps {
SELECT a FROM t1
WHERE +b IS NULL
OR c IS NULL
OR d IS NULL
ORDER BY a
}
} {90 91 92 96 97 99 scan 98 sort 0}
do_test where9-1.2.3 {
count_steps {
SELECT a FROM t1
WHERE b IS NULL
OR +c IS NULL
OR d IS NULL
ORDER BY a
}
} {90 91 92 96 97 99 scan 98 sort 0}
do_test where9-1.2.4 {
count_steps {
SELECT a FROM t1
WHERE b IS NULL
OR c IS NULL
OR +d IS NULL
ORDER BY a
}
} {90 91 92 96 97 99 scan 98 sort 0}
do_test where9-1.2.5 {
count_steps {
SELECT a FROM t4
WHERE b IS NULL
OR c IS NULL
OR d IS NULL
ORDER BY a
}
} {90 91 92 96 97 99 scan 98 sort 0}
do_test where9-1.3.1 {
count_steps {
SELECT a FROM t1
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
ORDER BY a
}
} {90 91 92 97 scan 0 sort 1}
do_test where9-1.3.2 {
count_steps {
SELECT a FROM t4
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
ORDER BY a
}
} {90 91 92 97 scan 98 sort 0}
do_test where9-1.3.3 {
count_steps {
SELECT a FROM t4
WHERE (b NOT NULL AND c NOT NULL AND d IS NULL)
OR (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
ORDER BY a
}
} {90 91 92 97 scan 98 sort 0}
do_test where9-1.3.4 {
count_steps {
SELECT a FROM (t4)
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
ORDER BY a
}
} {90 91 92 97 scan 98 sort 0}
do_test where9-1.4 {
count_steps {
SELECT a FROM t1
WHERE (b>=950 AND b<=1010) OR (b IS NULL AND c NOT NULL)
ORDER BY a
}
} {87 88 89 90 91 scan 0 sort 1}
do_test where9-1.5 {
# When this test was originally written, SQLite used a rowset object
# to optimize the "ORDER BY a" clause. Now that it is using a rowhash,
# this is not possible. So we have to comment out one term of the OR
# expression in order to prevent SQLite from deeming a full-table
# scan to be a better strategy than using multiple indexes, which would
# defeat the point of the test.
count_steps {
SELECT a FROM t1
WHERE a=83
OR b=913
OR c=28028
OR (d>=82 AND d<83)
/* OR (e>2802 AND e<2803) */
OR f='fghijklmn'
OR g='hgfedcb'
ORDER BY a
}
} {5 31 57 82 83 84 85 86 87 scan 0 sort 1}
do_test where9-1.6 {
count_steps {
SELECT a FROM t1
WHERE b=1012
OR (d IS NULL AND e IS NOT NULL)
}
} {92 scan 0 sort 0}
do_test where9-1.7 {
count_steps {
SELECT a FROM t1
WHERE (b=1012 OR (d IS NULL AND e IS NOT NULL))
AND f!=g
}
} {92 scan 0 sort 0}
do_test where9-1.8 {
count_steps {
SELECT a FROM t1
WHERE (b=1012 OR (d IS NULL AND e IS NOT NULL))
AND f==g
}
} {scan 0 sort 0}
do_test where9-2.1 {
count_steps {
SELECT t2.a FROM t1, t2
WHERE t1.a=80
AND (t1.c=t2.c OR t1.d=t2.d)
ORDER BY 1
}
} {79 80 81 scan 0 sort 1}
do_test where9-2.2 {
count_steps {
SELECT t2.a FROM t1, t2
WHERE t1.a=80
AND ((t1.c=t2.c AND t1.d=t2.d) OR t1.f=t2.f)
ORDER BY 1
}
} {2 28 54 80 scan 0 sort 1}
do_test where9-2.3 {
count_steps {
SELECT coalesce(t2.a,9999)
FROM t1 LEFT JOIN t2 ON (t1.c=t2.c AND t1.d=t2.d) OR t1.f=t2.f
WHERE t1.a=80
ORDER BY 1
}
} {2 28 54 80 scan 0 sort 1}
do_test where9-2.4 {
count_steps {
SELECT coalesce(t2.a,9999)
FROM t1 LEFT JOIN t2 ON (t1.c+1=t2.c AND t1.d=t2.d) OR (t1.f||'x')=t2.f
WHERE t1.a=80
ORDER BY 1
}
} {9999 scan 0 sort 1}
do_test where9-2.5 {
count_steps {
SELECT t1.a, coalesce(t2.a,9999)
FROM t1 LEFT JOIN t2 ON (t1.c=t2.c AND t1.d=t2.d) OR (t1.f)=t2.f
WHERE t1.a=80 OR t1.b=880 OR (t1.c=27027 AND round(t1.d)==80)
ORDER BY 1
}
} {80 80 80 2 80 28 80 54 scan 0 sort 1}
do_test where9-2.6 {
count_steps {
SELECT t1.a, coalesce(t2.a,9999)
FROM t1 LEFT JOIN t2 ON (t1.c+1=t2.c AND t1.d=t2.d) OR (t1.f||'x')=t2.f
WHERE t1.a=80 OR t1.b=880 OR (t1.c=27027 AND round(t1.d)==80)
ORDER BY 1
}
} {80 9999 scan 0 sort 1}
do_test where9-2.7 {
count_steps {
SELECT t3.x, t1.a, coalesce(t2.a,9999)
FROM t3 JOIN
t1 LEFT JOIN t2 ON (t1.c+1=t2.c AND t1.d=t2.d) OR (t1.f||'x')=t2.f
WHERE t1.a=t3.y OR t1.b=t3.y*11 OR (t1.c=27027 AND round(t1.d)==80)
ORDER BY 1, 2
}
} {1 80 9999 2 80 9999 scan 1 sort 1}
do_test where9-2.8 {
count_steps {
SELECT t3.x, t1.a, coalesce(t2.a,9999)
FROM t3 JOIN
t1 LEFT JOIN t2 ON (t1.c=t2.c AND t1.d=t2.d) OR (t1.f)=t2.f
WHERE t1.a=t3.y OR t1.b=t3.y*11 OR (t1.c=27027 AND round(t1.d)==80)
ORDER BY 1, 2, 3
}
} {1 80 2 1 80 28 1 80 54 1 80 80 2 80 2 2 80 28 2 80 54 2 80 80 scan 1 sort 1}
ifcapable explain {
do_eqp_test where9-3.1 {
SELECT t2.a FROM t1, t2
WHERE t1.a=80 AND ((t1.c=t2.c AND t1.d=t2.d) OR t1.f=t2.f)
} [string map {"\n " \n} {
QUERY PLAN
|--SEARCH t1 USING INTEGER PRIMARY KEY (rowid=?)
`--MULTI-INDEX OR
|--INDEX 1
| `--SEARCH t2 USING INDEX t2d (d=?)
`--INDEX 3
`--SEARCH t2 USING COVERING INDEX t2f (f=?)
}]
do_eqp_test where9-3.2 {
SELECT coalesce(t2.a,9999)
FROM t1 LEFT JOIN t2 ON (t1.c+1=t2.c AND t1.d=t2.d) OR (t1.f||'x')=t2.f
WHERE t1.a=80
} [string map {"\n " \n} {
QUERY PLAN
|--SEARCH t1 USING INTEGER PRIMARY KEY (rowid=?)
`--MULTI-INDEX OR
|--INDEX 1
| `--SEARCH t2 USING INDEX t2d (d=?)
`--INDEX 2
`--SEARCH t2 USING COVERING INDEX t2f (f=?)
}]
}
# Make sure that INDEXED BY and multi-index OR clauses play well with
# one another.
#
do_test where9-4.1 {
count_steps {
SELECT a FROM t1
WHERE b>1000
AND (c=31031 OR d IS NULL)
ORDER BY +a
}
} {92 93 97 scan 0 sort 1}
do_test where9-4.2 {
count_steps {
SELECT a FROM t1
WHERE b>1000
AND (c=31031 OR +d IS NULL)
ORDER BY +a
}
} {92 93 97 scan 0 sort 1}
do_test where9-4.3 {
count_steps {
SELECT a FROM t1
WHERE +b>1000
AND (c=31031 OR d IS NULL)
ORDER BY +a
}
} {92 93 97 scan 0 sort 1}
do_test where9-4.4 {
count_steps {
SELECT a FROM t1 INDEXED BY t1b
WHERE b>1000
AND (c=31031 OR d IS NULL)
ORDER BY +a
}
} {92 93 97 scan 0 sort 1}
do_test where9-4.5 {
catchsql {
SELECT a FROM t1 INDEXED BY t1b
WHERE +b>1000
AND (c=31031 OR d IS NULL)
ORDER BY +a
}
} {0 {92 93 97}}
do_test where9-4.6 {
count_steps {
SELECT a FROM t1 NOT INDEXED
WHERE b>1000
AND (c=31031 OR d IS NULL)
ORDER BY +a
}
} {92 93 97 scan 98 sort 1}
do_test where9-4.7 {
catchsql {
SELECT a FROM t1 INDEXED BY t1c
WHERE b>1000
AND (c=31031 OR d IS NULL)
ORDER BY +a
}
} {0 {92 93 97}}
do_test where9-4.8 {
catchsql {
SELECT a FROM t1 INDEXED BY t1d
WHERE b>1000
AND (c=31031 OR d IS NULL)
ORDER BY +a
}
} {0 {92 93 97}}
# The (c=31031 OR d IS NULL) clause is preferred over b>1000 because
# the former is an equality test which is expected to return fewer rows.
#
do_eqp_test where9-5.1 {
SELECT a FROM t1 WHERE b>1000 AND (c=31031 OR d IS NULL)
} {
QUERY PLAN
`--MULTI-INDEX OR
|--INDEX 1
| `--SEARCH t1 USING INDEX t1c (c=?)
`--INDEX 2
`--SEARCH t1 USING INDEX t1d (d=?)
}
# In contrast, b=1000 is preferred over any OR-clause.
#
do_eqp_test where9-5.2 {
SELECT a FROM t1 WHERE b=1000 AND (c=31031 OR d IS NULL)
} {SEARCH t1 USING INDEX t1b (b=?)}
# Likewise, inequalities in an AND are preferred over inequalities in
# an OR.
#
do_eqp_test where9-5.3 {
SELECT a FROM t1 WHERE b>1000 AND (c>=31031 OR d IS NULL)
} {SEARCH t1 USING INDEX t1b (b>?)}
############################################################################
# Make sure OR-clauses work correctly on UPDATE and DELETE statements.
do_test where9-6.2.1 {
db eval {SELECT count(*) FROM t1 UNION ALL SELECT a FROM t1 WHERE a>=85}
} {99 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99}
do_test where9-6.2.2 { ;# Deletes entries 90 91 92 96 97 99
count_steps {
BEGIN;
DELETE FROM t1
WHERE b IS NULL
OR c IS NULL
OR d IS NULL
}
} {scan 0 sort 0}
do_test where9-6.2.3 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a>=85;
ROLLBACK;
}
} {93 85 86 87 88 89 93 94 95 98}
do_test where9-6.2.4 { ;# Deletes entries 90 91 92 96 97 99
count_steps {
BEGIN;
DELETE FROM t1
WHERE +b IS NULL
OR c IS NULL
OR d IS NULL
}
} {scan 98 sort 0}
do_test where9-6.2.5 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a>=85;
ROLLBACK;
}
} {93 85 86 87 88 89 93 94 95 98}
do_test where9-6.2.6 {
count_steps {
BEGIN;
UPDATE t1 SET a=a+100
WHERE (b IS NULL
OR c IS NULL
OR d IS NULL)
AND a!=92
AND a!=97
}
} {scan 0 sort 0} ;# Add 100 to entries 90 91 96 99
do_test where9-6.2.7 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a>=85;
ROLLBACK
}
} {99 85 86 87 88 89 92 93 94 95 97 98 190 191 196 199}
do_test where9-6.2.8 { ;# Deletes entries 90 91 92 97 99
count_steps {
BEGIN;
DELETE FROM t1
WHERE (b IS NULL
OR c IS NULL
OR d IS NULL)
AND a!=96
}
} {scan 0 sort 0}
do_test where9-6.2.9 {
db eval {
SELECT count(*) FROM t1 UNION ALL SELECT a FROM t1 WHERE a>=85;
ROLLBACK;
}
} {94 85 86 87 88 89 93 94 95 96 98}
do_test where9-6.3.1 {
count_steps {
BEGIN;
DELETE FROM t1
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 0 sort 0} ;# DELETEs rows 90 91 92 97
do_test where9-6.3.2 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 100;
ROLLBACK;
}
} {95 85 86 87 88 89 93 94 95 96 98 99}
do_test where9-6.3.3 {
count_steps {
BEGIN;
UPDATE t1 SET a=a+100
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 0 sort 0} ;# Add 100 to rowids 90 91 92 97
do_test where9-6.3.4 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 200;
ROLLBACK;
}
} {99 85 86 87 88 89 93 94 95 96 98 99 190 191 192 197}
do_test where9-6.3.5 {
count_steps {
BEGIN;
DELETE FROM t1
WHERE (+b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 98 sort 0} ;# DELETEs rows 90 91 92 97
do_test where9-6.3.6 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 100;
ROLLBACK;
}
} {95 85 86 87 88 89 93 94 95 96 98 99}
do_test where9-6.3.7 {
count_steps {
BEGIN;
UPDATE t1 SET a=a+100
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND +c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 98 sort 0} ;# Add 100 to rowids 90 91 92 97
do_test where9-6.3.8 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 100;
ROLLBACK;
}
} {99 85 86 87 88 89 93 94 95 96 98 99}
do_test where9-6.4.1 {
count_steps {
BEGIN;
DELETE FROM t1
WHERE (b>=950 AND b<=1010) OR (b IS NULL AND c NOT NULL)
}
} {scan 0 sort 0} ;# DELETE rows 87 88 89 90 91
do_test where9-6.4.2 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 100;
ROLLBACK;
}
} {94 85 86 92 93 94 95 96 97 98 99}
do_test where9-6.4.3 {
count_steps {
BEGIN;
UPDATE t1 SET a=a+100
WHERE (b>=950 AND b<=1010) OR (b IS NULL AND c NOT NULL)
}
} {scan 0 sort 0} ;# Add 100 to rowids 87 88 89 90 91
do_test where9-6.4.4 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 100;
ROLLBACK;
}
} {99 85 86 92 93 94 95 96 97 98 99}
do_test where9-6.5.1 {
count_steps {
BEGIN;
DELETE FROM t1
WHERE a=83
OR b=913
OR c=28028
OR (d>=82 AND d<83)
OR (e>2802 AND e<2803)
OR f='fghijklmn'
OR g='hgfedcb'
}
} {scan 0 sort 0} ;# DELETE rows 5 31 57 82 83 84 85 86 87
do_test where9-6.5.2 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a IN (5,31,57,82,83,84,85,86,87);
ROLLBACK;
}
} {90}
do_test where9-6.5.3 {
count_steps {
BEGIN;
UPDATE t1 SET a=a+100
WHERE a=83
OR b=913
OR c=28028
OR (d>=82 AND d<83)
OR (e>2802 AND e<2803)
OR f='fghijklmn'
OR g='hgfedcb'
}
} {scan 0 sort 0} ;# Add 100 to rowids 5 31 57 82 83 84 85 86 87
do_test where9-6.5.4 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a%100 IN (5,31,57,82,83,84,85,86,87) ORDER BY rowid;
ROLLBACK;
}
} {99 105 131 157 182 183 184 185 186 187}
do_test where9-6.6.1 {
count_steps {
BEGIN;
DELETE FROM t1
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND +c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 98 sort 0} ;# DELETEs rows 90 91 92 97
do_test where9-6.6.2 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 100;
ROLLBACK;
}
} {95 85 86 87 88 89 93 94 95 96 98 99}
do_test where9-6.6.3 {
count_steps {
BEGIN;
UPDATE t1 SET a=a+100
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND +c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 98 sort 0} ;# Add 100 to rowids 90 91 92 97
do_test where9-6.6.4 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 200;
ROLLBACK;
}
} {99 85 86 87 88 89 93 94 95 96 98 99 190 191 192 197}
do_test where9-6.7.1 {
count_steps {
BEGIN;
DELETE FROM t1 NOT INDEXED
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 98 sort 0} ;# DELETEs rows 90 91 92 97
do_test where9-6.7.2 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 100;
ROLLBACK;
}
} {95 85 86 87 88 89 93 94 95 96 98 99}
do_test where9-6.7.3 {
count_steps {
BEGIN;
UPDATE t1 NOT INDEXED SET a=a+100
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {scan 98 sort 0} ;# Add 100 to rowids 90 91 92 97
do_test where9-6.7.4 {
db eval {
SELECT count(*) FROM t1 UNION ALL
SELECT a FROM t1 WHERE a BETWEEN 85 AND 200;
ROLLBACK;
}
} {99 85 86 87 88 89 93 94 95 96 98 99 190 191 192 197}
do_test where9-6.8.1 {
catchsql {
DELETE FROM t1 INDEXED BY t1b
WHERE (+b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {0 {}}
do_test where9-6.8.2 {
catchsql {
UPDATE t1 INDEXED BY t1b SET a=a+100
WHERE (+b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {0 {}}
set solution_possible 0
ifcapable stat4 {
if {[permutation] != "no_optimization"} { set solution_possible 1 }
}
if $solution_possible {
# When STAT3 is enabled, the "b NOT NULL" terms get translated
# into b>NULL, which can be satified by the index t1b. It is a very
# expensive way to do the query, but it works, and so a solution is possible.
do_test where9-6.8.3-stat4 {
catchsql {
UPDATE t1 INDEXED BY t1b SET a=a+100
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {0 {}}
do_test where9-6.8.4-stat4 {
catchsql {
DELETE FROM t1 INDEXED BY t1b
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {0 {}}
} else {
do_test where9-6.8.3 {
catchsql {
UPDATE t1 INDEXED BY t1b SET a=a+100
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {0 {}}
do_test where9-6.8.4 {
catchsql {
DELETE FROM t1 INDEXED BY t1b
WHERE (b IS NULL AND c NOT NULL AND d NOT NULL)
OR (b NOT NULL AND c IS NULL AND d NOT NULL)
OR (b NOT NULL AND c NOT NULL AND d IS NULL)
}
} {0 {}}
}
############################################################################
# Test cases where terms inside an OR series are combined with AND terms
# external to the OR clause. In other words, cases where
#
# x AND (y OR z)
#
# is able to use indices on x,y and x,z, or indices y,x and z,x.
#
do_test where9-7.0 {
execsql {
CREATE TABLE t5(a, b, c, d, e, f, g, x, y);
INSERT INTO t5
SELECT a, b, c, e, d, f, g,
CASE WHEN (a&1)!=0 THEN 'y' ELSE 'n' END,
CASE WHEN (a&2)!=0 THEN 'y' ELSE 'n' END
FROM t1;
CREATE INDEX t5xb ON t5(x, b);
CREATE INDEX t5xc ON t5(x, c);
CREATE INDEX t5xd ON t5(x, d);
CREATE INDEX t5xe ON t5(x, e);
CREATE INDEX t5xf ON t5(x, f);
CREATE INDEX t5xg ON t5(x, g);
CREATE INDEX t5yb ON t5(y, b);
CREATE INDEX t5yc ON t5(y, c);
CREATE INDEX t5yd ON t5(y, d);
CREATE INDEX t5ye ON t5(y, e);
CREATE INDEX t5yf ON t5(y, f);
CREATE INDEX t5yg ON t5(y, g);
CREATE TABLE t6(a, b, c, e, d, f, g, x, y);
INSERT INTO t6 SELECT * FROM t5;
ANALYZE t5;
}
} {}
do_test where9-7.1.1 {
count_steps {
SELECT a FROM t5 WHERE x='y' AND (b=913 OR c=27027) ORDER BY a;
}
} {79 81 83 scan 0 sort 1}
do_test where9-7.1.2 {
execsql {
SELECT a FROM t6 WHERE x='y' AND (b=913 OR c=27027) ORDER BY a;
}
} {79 81 83}
do_test where9-7.1.3 {
count_steps {
SELECT a FROM t5 WHERE x='n' AND (b=913 OR c=27027) ORDER BY a;
}
} {80 scan 0 sort 1}
do_test where9-7.1.4 {
execsql {
SELECT a FROM t6 WHERE x='n' AND (b=913 OR c=27027) ORDER BY a;
}
} {80}
do_test where9-7.2.1 {
count_steps {
SELECT a FROM t5 WHERE (x='y' OR y='y') AND b=913 ORDER BY a;
}
} {83 scan 0 sort 1}
do_test where9-7.2.2 {
execsql {
SELECT a FROM t6 WHERE (x='y' OR y='y') AND b=913 ORDER BY a;
}
} {83}
do_test where9-7.3.1 {
count_steps {
SELECT a FROM t5 WHERE (x='y' OR y='y') AND c=27027 ORDER BY a;
}
} {79 81 scan 0 sort 1}
do_test where9-7.3.2 {
execsql {
SELECT a FROM t6 WHERE (x='y' OR y='y') AND c=27027 ORDER BY a;
}
} {79 81}
# Fix for ticket [b7c8682cc17f32903f03a610bd0d35ffd3c1e6e4]
# "Incorrect result from LEFT JOIN with OR in the WHERE clause"
#
do_test where9-8.1 {
db eval {
CREATE TABLE t81(a INTEGER PRIMARY KEY, b, c, d);
CREATE TABLE t82(x INTEGER PRIMARY KEY, y);
CREATE TABLE t83(p INTEGER PRIMARY KEY, q);
INSERT INTO t81 VALUES(2,3,4,5);
INSERT INTO t81 VALUES(3,4,5,6);
INSERT INTO t82 VALUES(2,4);
INSERT INTO t83 VALUES(5,55);
SELECT *
FROM t81 LEFT JOIN t82 ON y=b JOIN t83
WHERE c==p OR d==p
ORDER BY +a;
}
} {2 3 4 5 {} {} 5 55 3 4 5 6 2 4 5 55}
do_test where9-8.2 {
db eval {
SELECT *
FROM t81 LEFT JOIN (t82) ON y=b JOIN t83
WHERE c==p OR d==p
ORDER BY +a;
}
} {2 3 4 5 {} {} 5 55 3 4 5 6 2 4 5 55}
do_test where9-8.3 {
db eval {
SELECT *
FROM (t81) LEFT JOIN (main.t82) ON y=b JOIN t83
WHERE c==p OR d==p
ORDER BY +a;
}
} {2 3 4 5 {} {} 5 55 3 4 5 6 2 4 5 55}
# Fix for ticket [f2369304e47167e3e644e2f1fe9736063391d7b7]
# Incorrect results when OR is used in the ON clause of a LEFT JOIN
#
do_test where9-9.1 {
db eval {
CREATE TABLE t91(x); INSERT INTO t91 VALUES(1);
CREATE TABLE t92(y INTEGER PRIMARY KEY,a,b);
INSERT INTO t92 VALUES(1,2,3);
SELECT 1 FROM t91 LEFT JOIN t92 ON a=2 OR b=3;
SELECT 2 FROM t91 LEFT JOIN t92 ON a=2 AND b=3;
SELECT 3 FROM t91 LEFT JOIN t92 ON (a=2 OR b=3) AND y IS NULL;
SELECT 4 FROM t91 LEFT JOIN t92 ON (a=2 AND b=3) AND y IS NULL;
CREATE TEMP TABLE x9 AS SELECT * FROM t91 LEFT JOIN t92 ON a=2 OR b=3;
SELECT 5 FROM x9 WHERE y IS NULL;
SELECT 6 FROM t91 LEFT JOIN t92 ON a=2 OR b=3 WHERE y IS NULL;
SELECT 7 FROM t91 LEFT JOIN t92 ON a=2 AND b=3 WHERE y IS NULL;
SELECT 8 FROM t91 LEFT JOIN t92 ON a=22 OR b=33 WHERE y IS NULL;
SELECT 9 FROM t91 LEFT JOIN t92 ON a=22 AND b=33 WHERE y IS NULL;
}
} {1 2 3 4 8 9}
# Fix for ticket [bc878246eafe0f52c519e29049b2fe4a99491b27]
# Incorrect result when OR is used in a join to the right of a LEFT JOIN
#
do_test where9-10.1 {
db eval {
CREATE TABLE t101 (id INTEGER PRIMARY KEY);
INSERT INTO t101 VALUES (1);
SELECT * FROM t101 AS t0
LEFT JOIN t101 AS t1 ON t1.id BETWEEN 10 AND 20
JOIN t101 AS t2 ON (t2.id = t0.id OR (t2.id<>555 AND t2.id=t1.id));
}
} {1 {} 1}
do_test where9-10.2 {
db eval {
CREATE TABLE t102 (id TEXT UNIQUE NOT NULL);
INSERT INTO t102 VALUES ('1');
SELECT * FROM t102 AS t0
LEFT JOIN t102 AS t1 ON t1.id GLOB 'abc%'
JOIN t102 AS t2 ON (t2.id = t0.id OR (t2.id<>555 AND t2.id=t1.id));
}
} {1 {} 1}
# dbsqlfuzz 9df1d53c24c4c96af0dae15ee764897af415ac76
# The MULTI-INDEX OR processing evaluates the same WHERE-clause sub-expression
# twice. But if that sub-expression contains a UNION ALL SELECT statement
# subject to query flattening, the sub-expression might be transformed in a
# way that it can only be code-generated once. An assert() will fail on
# the second attempt to generate code from the same sub-expression.
# The solution is to make a copy of sub-expressions used by MULTI-INDEX OR
#
reset_db
do_execsql_test where9-11.1 {
CREATE TABLE t1(a INTEGER PRIMARY KEY, b TEXT);
CREATE TABLE t2_a(k INTEGER PRIMARY KEY, v TEXT);
CREATE TABLE t2_b(k INTEGER PRIMARY KEY, v TEXT);
CREATE VIEW t2 AS SELECT * FROM t2_a UNION ALL SELECT * FROM t2_b;
SELECT 1 FROM t1 JOIN t1 USING(a)
WHERE (a=1)
OR (a=2 AND (SELECT 4 FROM t2,(SELECT 5 FROM t1 ORDER BY a) WHERE a));
} {}
finish_test
Reference in New Issue View Git Blame Copy Permalink