Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a typo in the "key format" documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
4beefed2c96136826015b6c0a6833680 |
User & Date: | drh 2013-07-18 00:58:38.715 |
Context
2013-07-22
| ||
12:28 | Changes necessary to get TH4 to compile again. check-in: 15e8dd41a9 user: drh tags: trunk | |
2013-07-18
| ||
00:58 | Fix a typo in the "key format" documentation. check-in: 4beefed2c9 user: drh tags: trunk | |
2013-07-06
| ||
23:14 | Add tests for sqlite4_num_sub with inf and nan. check-in: ed79d6f7fa user: peterreid tags: trunk | |
Changes
Changes to www/key_encoding.wiki.
1 2 3 4 5 6 7 8 | <title>Key Encoding</title> This note describes how record keys are encoded. The encoding is designed such that memcmp() can be used to sort the keys into their proper order. A key consists of a table number followed by a list of one or more SQL values. Each SQL value in the list has one of the following types: NULL, numeric, text, or binary. Keys are compared value by value, from left to | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | <title>Key Encoding</title> This note describes how record keys are encoded. The encoding is designed such that memcmp() can be used to sort the keys into their proper order. A key consists of a table number followed by a list of one or more SQL values. Each SQL value in the list has one of the following types: NULL, numeric, text, or binary. Keys are compared value by value, from left to right, until a difference is found. The first difference determines the key order. The table number is a [./varint.wiki | varint] that identifies the table to which the key belongs. Table numbers always sort in ASCENDING order. Each SQL value has a sort-order which is either ASCENDING or DESCENDING. The |
︙ | ︙ |