Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | More typo fixes. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
8f9d1225b61bde1593de941c7a9f31f6 |
User & Date: | drh 2011-06-20 23:51:12.106 |
Context
2011-06-21
| ||
00:17 | Add a news item for the 3.7.7 release. (check-in: 4bfe2f0bdf user: drh tags: trunk) | |
2011-06-20
| ||
23:51 | More typo fixes. (check-in: 8f9d1225b6 user: drh tags: trunk) | |
21:48 | Documentation typos. (check-in: b503d1f516 user: drh tags: trunk) | |
Changes
Changes to pages/fileio.in.
︙ | ︙ | |||
263 264 265 266 267 268 269 | written to the file system just before or during the failure. The exact combination of IO operations that SQLite is required to perform in order to safely modify a database file depend on the exact characteristics of the target platform. <p> This section describes the assumptions that SQLite makes about the | | | 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 | written to the file system just before or during the failure. The exact combination of IO operations that SQLite is required to perform in order to safely modify a database file depend on the exact characteristics of the target platform. <p> This section describes the assumptions that SQLite makes about the content of a file-system following a power or system failure. In other words, it describes the extent of file and file-system corruption that such an event may cause. <p> SQLite queries an implementation for file-system characteristics using the xDeviceCharacteristics() and xSectorSize() methods of the database file file-handle. These two methods are only ever called |
︙ | ︙ | |||
463 464 465 466 467 468 469 | ASSUMPTION A21004 If a system failure occurs during a "delete file" operation, it is assumed that following system recovery the file-system will either contain the file being deleted in the state it was in before the operation was attempted, or not contain the file at all. It is assumed that it is not possible for the file to have become corrupted | | | 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 | ASSUMPTION A21004 If a system failure occurs during a "delete file" operation, it is assumed that following system recovery the file-system will either contain the file being deleted in the state it was in before the operation was attempted, or not contain the file at all. It is assumed that it is not possible for the file to have become corrupted purely as a result of a failure occurring during a "delete file" operation. <p> The effects of a <b>truncate file</b> operation are not assumed to be made persistent until after the corresponding file has been <i>synced</i>. |
︙ | ︙ |
Changes to pages/lang.in.
︙ | ︙ | |||
1928 1929 1930 1931 1932 1933 1934 | the value that can be interpreted as an integer number is extracted from the TEXT value and the remainder ignored. ^Any leading spaces in the TEXT value when converting from TEXT to INTEGER are ignored. ^If there is no prefix that can be interpreted as an integer number, the result of the conversion is 0. <p>^A cast of a REAL value into an INTEGER will truncate the fractional | | | 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 | the value that can be interpreted as an integer number is extracted from the TEXT value and the remainder ignored. ^Any leading spaces in the TEXT value when converting from TEXT to INTEGER are ignored. ^If there is no prefix that can be interpreted as an integer number, the result of the conversion is 0. <p>^A cast of a REAL value into an INTEGER will truncate the fractional part of the REAL. ^If a REAL is too large to be represented as an INTEGER then the result of the cast is the largest negative integer: -9223372036854775808. <tr> <td> NUMERIC <td> ^Casting a TEXT or BLOB value into NUMERIC first does a forced conversion into REAL but then further converts the result into INTEGER if |
︙ | ︙ |
Changes to pages/nulls.in.
︙ | ︙ | |||
11 12 13 14 15 16 17 | be handled in all circumstances. </p> <p> So instead of going by the standards documents, various popular SQL engines were tested to see how they handle NULLs. The idea was to make SQLite work like all the other engines. | | | 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 | be handled in all circumstances. </p> <p> So instead of going by the standards documents, various popular SQL engines were tested to see how they handle NULLs. The idea was to make SQLite work like all the other engines. An SQL test script was developed and run by volunteers on various SQL RDBMSes and the results of those tests were used to deduce how each engine processed NULL values. The original tests were run in May of 2002. A copy of the test script is found at the end of this document. </p> <p> |
︙ | ︙ |
Changes to pages/rtree.in.
︙ | ︙ | |||
92 93 94 95 96 97 98 | <em><name></em><strong>_node</strong><br> <em><name></em><strong>_rowid</strong><br> <em><name></em><strong>_parent</strong> </blockquote>)^ <p> ^The shadow tables are ordinary SQLite data tables. You can query them | | | 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 | <em><name></em><strong>_node</strong><br> <em><name></em><strong>_rowid</strong><br> <em><name></em><strong>_parent</strong> </blockquote>)^ <p> ^The shadow tables are ordinary SQLite data tables. You can query them directly if you like, though this unlikely to reveal anything particularly useful. ^And you can [UPDATE], [DELETE], [INSERT] or even [DROP TABLE | DROP] the shadow tables, though doing so will corrupt your R*Tree index. So it is best to simply ignore the shadow tables. Recognize that they are there to hold your R*Tree index information and let it go as that. </p> |
︙ | ︙ |