Documentation Source Text

Check-in [2112591627]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix a documentation error pointed out by Richard Godbee on the mailing list.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 21125916278bcb4ded9771143680a7b1fd806b80
User & Date: drh 2011-11-17 14:59:31.315
Context
2011-11-17
18:03
Update the "changes" log for the next release. Fix all hyperlinks. (check-in: 4643d06dfe user: drh tags: trunk)
14:59
Fix a documentation error pointed out by Richard Godbee on the mailing list. (check-in: 2112591627 user: drh tags: trunk)
2011-11-11
13:37
Rerender all bubble-diagram gifs using xvnc on "elly". The choice of X-server makes a huge difference in the final output, unfortunately. (check-in: d8b1c2a562 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/eqp.in.
︙︙
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

    sqlite> EXPLAIN QUERY PLAN SELECT a, b FROM t1 WHERE a=1; 
    0|0|0|SCAN TABLE t1 (~100000 rows)
</codeblock>)^

<p>
  The example above shows
  SQLite estimating that the full-table scan will visit approximately 
  1,000,000 records. If the query were able to use an index, then the 
  SCAN/SEARCH record would include the name of the index and, for a
  SEARCH record, an indication of how the subset of rows visited is
  identified. For example:
^(<codeblock>
    sqlite&gt; CREATE INDEX i1 ON t1(a);
    sqlite&gt; EXPLAIN QUERY PLAN SELECT a, b FROM t1 WHERE a=1;
    0|0|0|SEARCH TABLE t1 USING INDEX i1 (a=?) (~10 rows)








|








64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

    sqlite&gt; EXPLAIN QUERY PLAN SELECT a, b FROM t1 WHERE a=1; 
    0|0|0|SCAN TABLE t1 (~100000 rows)
</codeblock>)^

<p>
  The example above shows
  SQLite estimating that the full-table scan will visit approximately 
  100,000 records. If the query were able to use an index, then the 
  SCAN/SEARCH record would include the name of the index and, for a
  SEARCH record, an indication of how the subset of rows visited is
  identified. For example:
^(<codeblock>
    sqlite&gt; CREATE INDEX i1 ON t1(a);
    sqlite&gt; EXPLAIN QUERY PLAN SELECT a, b FROM t1 WHERE a=1;
    0|0|0|SEARCH TABLE t1 USING INDEX i1 (a=?) (~10 rows)
︙︙