diff options
author | drh <drh@noemail.net> | 2018-05-02 18:00:17 +0000 |
---|---|---|
committer | drh <drh@noemail.net> | 2018-05-02 18:00:17 +0000 |
commit | b3f0276b9e4fd6465aaefa6e527d3f7a19a59b8c (patch) | |
tree | c9f50dc49d86bbddef84d7e52539152f908e1b4c /test/skipscan6.test | |
parent | 84a01debf9cd527e422d4bc3cbd0149b8a3b9e34 (diff) | |
download | sqlite-b3f0276b9e4fd6465aaefa6e527d3f7a19a59b8c.tar.gz sqlite-b3f0276b9e4fd6465aaefa6e527d3f7a19a59b8c.zip |
Fix test cases so that they work with the new EXPLAIN QUERY PLAN output
format. Only some of the cases have been fixed. This is an incremental
check-in.
FossilOrigin-Name: 5f0e803e33aa557865d5fc830d9202d628de9a94c9757058ca48f1a560702cd3
Diffstat (limited to 'test/skipscan6.test')
-rw-r--r-- | test/skipscan6.test | 13 |
1 files changed, 2 insertions, 11 deletions
diff --git a/test/skipscan6.test b/test/skipscan6.test index 026c4d7b0..a53be1d95 100644 --- a/test/skipscan6.test +++ b/test/skipscan6.test @@ -179,22 +179,13 @@ do_execsql_test 3.0 { # do_eqp_test 3.1 { SELECT * FROM t3 WHERE a = ? AND c = ? -} { - 0 0 0 {SEARCH TABLE t3 USING INDEX t3_a (a=?)} -} +} {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 - - - +} {SEARCH TABLE t2 USING INDEX t2_a (a=?)} finish_test |