Searched refs:scan (Results 1 – 25 of 115) sorted by relevance
12345
66 } {2 3 scan 0 sort 1}71 } {2 3 scan 4 sort 0}76 } {2 3 scan 4 sort 0}128 } {3 scan 4 sort 0}133 } {3 scan 4 sort 0}142 } {scan 0 sort 1}150 } {5 scan 0 sort 1}158 } {5 scan 0 sort 1}166 } {5 scan 0 sort 1}175 } {scan 0 sort 1}[all …]
275 } {92 scan 0 sort 0}282 } {92 scan 0 sort 0}289 } {scan 0 sort 0}322 } {9999 scan 0 sort 1}338 } {80 9999 scan 0 sort 1}497 } {scan 0 sort 0}515 } {scan 98 sort 0}554 } {scan 0 sort 0}878 } {80 scan 0 sort 1}888 } {83 scan 0 sort 1}[all …]
12 # This file implements tests of the "skip-scan" query strategy.15 # the skip-scan query strategy in the "optoverview.html" document.59 # Without ANALYZE, a skip-scan is not used69 # Now do an ANALYZE. A skip-scan can be used after ANALYZE.74 -- of a skip-scan. So make a manual adjustment to the stat1 table105 # skip-scan should not be used after an (unfudged) ANALYZE.130 # skip-scan will be used after an (unfudged) ANALYZE.174 # Now do an ANALYZE. A skip-scan can be used after ANALYZE.188 # A skip-scan on a PK index of a WITHOUT ROWID table.
12 # This file implements tests of the "skip-scan" query strategy.190 # Ticket 520070ec7fbaac: Array overrun in the skip-scan optimization212 # Make sure skip-scan cost computation in the query planner takes into247 # The column used by the skip-scan needs to be sufficiently selective.257 -- Only two distinct values for the skip-scan column. Skip-scan is not used.263 -- Four distinct values for the skip-scan column. Skip-scan is used.269 -- Two distinct values for the skip-scan column again. Skip-scan is not used.325 # A skip-scan with a "column IN (SELECT ...)" on the second term of the340 optimization_control db skip-scan 0345 optimization_control db skip-scan 1
12 # Test cases for ORDER BY and LIMIT on an index scan.38 # Prior to the fix, the following EQP would show a table scan and a sort39 # rather than an index scan.47 # then we should (correctly) revert to using a table scan.
694 } {xyz scan 0 sort 0}699 } {xyz scan 19 sort 0}781 } {12 123 scan 5 like 6}786 } {12 123 scan 5 like 6}791 } {12 123 scan 5 like 6}796 } {12 123 scan 5 like 6}814 } {12 123 scan 5 like 6}830 } {12 123 scan 5 like 6}835 } {12 123 scan 5 like 6}840 } {12 123 scan 5 like 6}[all …]
12 # This file implements tests of the "skip-scan" query strategy.15 # "WHERE a=?1 AND c=?2" - verify that skip-scan can still be used.30 # This version has long used skip-scan because of the "+a"39 # This version (with "a" instead of "+a") should use skip-scan but
21 # and the number of full-scan steps.25 lappend r scan [db status step] sort [db status sort]58 } {1 2 three scan 0 sort 0}
12 # This file implements tests of the "skip-scan" query strategy. In 14 # is always preferred over the use of a skip-scan on some columns of15 # the same index. Because of difficulties in scoring a skip-scan,16 # the skip-scan can sometimes come out with a lower raw score when18 # full index rather than the skip-scan.185 # same reason. At one point though, it was mistakenly using a skip-scan.
24 set scan(littleEndian) i*25 set scan(bigEndian) I*26 binary scan $blob $scan($::tcl_platform(byteOrder)) r
12 # This file implements tests of the "skip-scan" query strategy. In 14 # that uses the skip-scan approach.67 # Test that range-query/skip-scan estimation works with text values.120 # Test that range-query/skip-scan estimation works on columns that contain
13 # for a full-table scan (under the theory that the index will be smaller30 # covering index used for the scan, hence values are increasing48 optimization_control db cover-idx-scan 0
166 set scan(littleEndian) i*167 set scan(bigEndian) I*168 binary scan $blob $scan($::tcl_platform(byteOrder)) r
75 set scan(littleEndian) i*76 set scan(bigEndian) I*77 binary scan $blob $scan($::tcl_platform(byteOrder)) r
32 set scan(littleEndian) i*33 set scan(bigEndian) I*34 binary scan $blob $scan($::tcl_platform(byteOrder)) r
185 binary scan $zCelloffset S iCelloffset233 binary scan $zCelloffset S iCelloffset238 binary scan $zCelloffset S iCelloffset398 binary scan $zRightChild I iRightChild416 binary scan $zCellOffset S iCellOffset419 binary scan $zChild I iChild437 binary scan $zRightChild I iRightChild465 binary scan $zRightChild I iRightChild
59 # Linear scan.88 # Linear scan of t1.109 # Linear scan125 # Linear scan
107 # a full table scan is required.118 # table scan is required.131 # a full table scan is required.142 # table scan is required.
96 set scan(littleEndian) i*97 set scan(bigEndian) I*98 binary scan $blob $scan($::tcl_platform(byteOrder)) r
29 binary scan $expect \c* expectvals30 binary scan $got \c* gotvals37 binary scan $utf16 \c* ints
26 set scan(littleEndian) i*27 set scan(bigEndian) I*28 binary scan $blob $scan($::tcl_platform(byteOrder)) r
160 set scan(littleEndian) i*161 set scan(bigEndian) I*162 binary scan $blob $scan($::tcl_platform(byteOrder)) r
22 set scan(littleEndian) i*23 set scan(bigEndian) I*24 binary scan $blob $scan($::tcl_platform(byteOrder)) r284 # use the full-text index (i.e. lookup by rowid or full-table scan).
9 scan-build gcc -c -DHAVE_STDINT_H -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_RTREE \12 scan-build gcc -c -I. -DSQLITE_ENABLE_STAT3 -DSQLITE_THREADSAFE=0 \
37 binary scan $blob I* ints44 binary scan $blob I* ints