Documentation Source Text

Check-in [d1d2571bce]
Login

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

Overview
Comment:Fix another typo in queryplanner.in.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: d1d2571bcef53d1791f3d2490ddf748786b73168
User & Date: drh 2013-05-14 11:14:12.524
Context
2013-05-15
18:58
Add recent bug fixes to the 3.7.17 change log. (check-in: 2b8ea61f51 user: drh tags: trunk)
2013-05-14
11:14
Fix another typo in queryplanner.in. (check-in: d1d2571bce user: drh tags: trunk)
11:12
Fix a typo in queryplanner.html. (check-in: d52ed00775 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/queryplanner.in.
︙︙
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329


<p>
A multi-column index follows the same pattern as a single-column index;
the indexed columns are added in front of the rowid.  The only difference
is that now multiple columns are added.  The left-most column is the
primary key used for ordering the rows in the index.  The second column is
used to break ties in the left-most column.  If there were a third column,
it would be used to break ties for the first to columns.  And so forth for
as many columns as their are in the index.  Because rowid is guaranteed
to be unique, every row of the index will be unique even if all of the
content columns for two rows are the same.  That case does not happen
in our sample data, but there is one case (fruit='Orange') where there
is a tie on the first column which must be broken by the second column.
</p>









|








315
316
317
318
319
320
321
322
323
324
325
326
327
328
329


<p>
A multi-column index follows the same pattern as a single-column index;
the indexed columns are added in front of the rowid.  The only difference
is that now multiple columns are added.  The left-most column is the
primary key used for ordering the rows in the index.  The second column is
used to break ties in the left-most column.  If there were a third column,
it would be used to break ties for the first two columns.  And so forth for
as many columns as their are in the index.  Because rowid is guaranteed
to be unique, every row of the index will be unique even if all of the
content columns for two rows are the same.  That case does not happen
in our sample data, but there is one case (fruit='Orange') where there
is a tie on the first column which must be broken by the second column.
</p>
︙︙