Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix documentation typo in fileformat.html. |
|---|---|
| Timelines: | family | ancestors | descendants | both | branch-3.31 |
| Files: | files | file ages | folders |
| SHA3-256: |
5dacf1a573c2034d7fa5a36dd0293451 |
| User & Date: | drh 2020-03-03 18:22:29 |
Context
|
2020-03-12
| ||
| 20:03 | Update the support page to direct users to the SQLite Forum instead of to the mailing lists. check-in: 2a8e648db7 user: drh tags: branch-3.31 | |
|
2020-03-03
| ||
| 18:22 | Fix documentation typo in fileformat.html. check-in: 5dacf1a573 user: drh tags: branch-3.31 | |
|
2020-02-26
| ||
| 11:09 | Fix a formatting problem in rescode.html. check-in: d35032eb7f user: drh tags: branch-3.31 | |
Changes
Changes to pages/fileformat2.in.
1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 |
<p>^(In the extreme case where the columns being indexed cover all columns of the PRIMARY KEY, the index will consist of only the columns being indexed. The ex25acde example above demonstrates this.)^ ^Each entry in the ex25acde index consists of only the columns a, c, d, and e, in that order.</p> <p>Each row in ex25ae contains five columns: c, e, d, c, a. The c column is repeated since the first occurrence of c has a collating function of "nocase" and the second has a collating sequence of "binary". If the c column is not repeated and if the table contains two or more entries with the same e value and where c differs only in case, then all of those table entries would correspond to a single entry in the index, which would break the one-to-one correspondence between the table and the index. <p> ^The suppression of redundant columns in the key suffix of an index entry only occurs in WITHOUT ROWID tables. ^In an ordinary rowid table, the index entry always ends with the rowid even if the [INTEGER PRIMARY KEY] |
| | | | |
1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 |
<p>^(In the extreme case where the columns being indexed cover all columns of the PRIMARY KEY, the index will consist of only the columns being indexed. The ex25acde example above demonstrates this.)^ ^Each entry in the ex25acde index consists of only the columns a, c, d, and e, in that order.</p> <p>Each row in ex25ae contains five columns: a, e, d, c, a. The "a" column is repeated since the first occurrence of "a" has a collating function of "nocase" and the second has a collating sequence of "binary". If the "a" column is not repeated and if the table contains two or more entries with the same "e" value and where "a" differs only in case, then all of those table entries would correspond to a single entry in the index, which would break the one-to-one correspondence between the table and the index. <p> ^The suppression of redundant columns in the key suffix of an index entry only occurs in WITHOUT ROWID tables. ^In an ordinary rowid table, the index entry always ends with the rowid even if the [INTEGER PRIMARY KEY] |