Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add a test case to check that the previous commit is effective. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
948d6e5d07bc14b6de32ec2144c716a5 |
User & Date: | dan 2014-11-05 14:19:05.905 |
Context
2014-11-05
| ||
15:57 | Make sure that NULL results from OP_Column are fully and completely NULL and do not have the MEM_Ephem bit set. Fix for ticket [094d39a4c95ee4]. (check-in: 42705fd7d8 user: drh tags: trunk) | |
14:19 | Add a test case to check that the previous commit is effective. (check-in: 948d6e5d07 user: dan tags: trunk) | |
13:13 | Enhance whereLoopCheaperProperSubset(X,Y) so that it does not report true if X uses skip-scan less than Y, since in that case X might deserve to be cheaper even if it is a proper subset. (check-in: c106b75536 user: drh tags: trunk) | |
Changes
Changes to test/skipscan6.test.
︙ | ︙ | |||
135 136 137 138 139 140 141 142 143 144 145 | EXPLAIN QUERY PLAN SELECT COUNT(*) FROM t1 WHERE bb=21 AND aa=1 AND dd BETWEEN 1413833728 and 1413837331; } {/INDEX good .bb=. AND aa=. AND dd>. AND dd<../} finish_test | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 | EXPLAIN QUERY PLAN SELECT COUNT(*) FROM t1 WHERE bb=21 AND aa=1 AND dd BETWEEN 1413833728 and 1413837331; } {/INDEX good .bb=. AND aa=. AND dd>. AND dd<../} # Create a table containing 100 rows. Column "a" contains a copy of the # rowid value - sequentially increasing integers from 1 to 100. Column # "b" contains the value of (a % 5). Columns "c" and "d" both contain # constant values (i.e. the same for every row). # # Then create a second table t2. t2 is the same as t3 except for the # order in which the indexes are created. # do_execsql_test 3.0 { CREATE TABLE t3(a, b, c, d); CREATE INDEX t3_ba ON t3(b, a, c); CREATE INDEX t3_a ON t3(a); WITH d(a, b) AS ( SELECT 1, 1 UNION ALL SELECT a+1, (a+1) % 5 FROM d WHERE a<100 ) INSERT INTO t3 SELECT a, b, 'c', 'd' FROM d; CREATE TABLE t2(a, b, c, d); CREATE INDEX t2_a ON t2(a); CREATE INDEX t2_ba ON t2(b, a, c); INSERT INTO t2 SELECT * FROM t3; ANALYZE; SELECT * FROM sqlite_stat1; } { t2 t2_ba {100 20 1 1} t2 t2_a {100 1} t3 t3_a {100 1} t3 t3_ba {100 20 1 1} } # Use index "t3_a", as (a=?) is expected to match only a single row. # do_eqp_test 3.1 { SELECT * FROM t3 WHERE a = ? AND c = ? } { 0 0 0 {SEARCH TABLE t3 USING INDEX t3_a (a=?)} } # The same query on table t2. This should use index "t2_a", for the # same reason. At one point though, it was mistakenly using a skip-scan. # do_eqp_test 3.2 { SELECT * FROM t2 WHERE a = ? AND c = ? } { 0 0 0 {SEARCH TABLE t2 USING INDEX t2_a (a=?)} } finish_test finish_test |