Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a couple typos in the new docs. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
255ed0fac7c0fc6bf067e9fa7fbc26ac |
User & Date: | mistachkin 2015-10-07 22:42:00.037 |
Context
2015-10-08
| ||
00:21 | Minor English grammar changes. (check-in: 543413f753 user: drh tags: trunk) | |
2015-10-07
| ||
22:42 | Fix a couple typos in the new docs. (check-in: 255ed0fac7 user: mistachkin tags: trunk) | |
19:40 | Link the optoverview.html document to the new expridx.html document. (check-in: 47d33de042 user: drh tags: trunk) | |
Changes
Changes to pages/json1.in.
︙ | ︙ | |||
154 155 156 157 158 159 160 | <p> The json1 extension (currently) stores JSON as ordinary text. <p> Backwards compatibility constraints mean that SQLite is only able to store values that are NULL, integers, floating-point numbers, text, | | | 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 | <p> The json1 extension (currently) stores JSON as ordinary text. <p> Backwards compatibility constraints mean that SQLite is only able to store values that are NULL, integers, floating-point numbers, text, and BLOBs. It is not possible to add a sixth "JSON" type. <p> The json1 extension does not (currently) support a binary encoding of JSON. Experiments have so far been unable to find a binary encoding that is significantly smaller or faster than a plain text encoding. (The present implementation parses JSON text at over 300 MB/s.) All json1 functions currently throw an error if any of their |
︙ | ︙ | |||
208 209 210 211 212 213 214 | <h3>2.3 VALUE arguments</h3> <p> For functions that accept "<i>value</i>" arguments (also shown as "<i>value1</i>" and "<i>value2</i>"), those arguments is usually understood to be a literal strings that are quoted and becomes JSON string values | | | 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 | <h3>2.3 VALUE arguments</h3> <p> For functions that accept "<i>value</i>" arguments (also shown as "<i>value1</i>" and "<i>value2</i>"), those arguments is usually understood to be a literal strings that are quoted and becomes JSON string values in the result. Even if the input <i>value</i> strings look like well-formed JSON, they are still interpreted as literal strings in the result. <p> However, if a <i>value</i> argument come directly from the result of another json1 function, then the argument is understood to be actual JSON and the complete JSON is inserted rather than a quoted string. |
︙ | ︙ |
Changes to pages/vtab.in.
︙ | ︙ | |||
145 146 147 148 149 150 151 | [CREATE VIRTUAL TABLE] statements are prohibited for that virtual table, and the virtual table is an "eponymous-only virtual table". Eponymous-only virtual tables are useful as [table-valued functions]. <p> Note that SQLite versions prior to 3.8.12 did not check the xCreate method | | | 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 | [CREATE VIRTUAL TABLE] statements are prohibited for that virtual table, and the virtual table is an "eponymous-only virtual table". Eponymous-only virtual tables are useful as [table-valued functions]. <p> Note that SQLite versions prior to 3.8.12 did not check the xCreate method for NULL before invoking it. So if an eponymous-only virtual table is registered with SQLite version 3.8.11.1 or earlier and a [CREATE VIRTUAL TABLE] command is attempted against that virtual table module, a jump to a NULL pointer will occur, resulting in a crash. <h3>1.2 Implementation</h3> <p>Several new C-level objects are used by the virtual table implementation: |
︙ | ︙ |