Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Another minor change to the EQP documentation. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
1aff2310137e184b125386e9c1b44309 |
| User & Date: | drh 2010-11-18 01:11:35 |
Context
|
2010-11-18
| ||
| 16:21 | Update the documentation to be explicit that a parent key must not be a rowid. check-in: d1edb27943 user: drh tags: trunk | |
| 01:11 | Another minor change to the EQP documentation. check-in: 1aff231013 user: drh tags: trunk | |
|
2010-11-17
| ||
| 22:30 | Tweak to the text of the EQP documentation. check-in: 5f2171a4cb user: drh tags: trunk | |
Changes
Changes to pages/eqp.in.
50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 |
following information:
<ul>
<li> The name of the table data is read from.
<li> Whether or not an index or [automatic indexing|automatic index] is used.
<li> Whether or not the [covering index] optimization applies.
<li> Which terms of the WHERE clause are used for indexing.
<li> The estimated number of rows that SQLite expects the scan to visit.
</ul>)^
<p>
For example, the following EXPLAIN QUERY PLAN command operates on a SELECT
statement that is implemented by performing a full-table scan on table t1:
^(<codeblock>
sqlite> EXPLAIN QUERY PLAN SELECT a, b FROM t1 WHERE a=1;
|
| |
50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 |
following information:
<ul>
<li> The name of the table data is read from.
<li> Whether or not an index or [automatic indexing|automatic index] is used.
<li> Whether or not the [covering index] optimization applies.
<li> Which terms of the WHERE clause are used for indexing.
<li> The estimated number of rows that SQLite will visit.
</ul>)^
<p>
For example, the following EXPLAIN QUERY PLAN command operates on a SELECT
statement that is implemented by performing a full-table scan on table t1:
^(<codeblock>
sqlite> EXPLAIN QUERY PLAN SELECT a, b FROM t1 WHERE a=1;
|