Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix documentation typos. Tickets #2168 and #2560. (CVS 4201) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
4333b231af8866e3d2d75bc64083b6c3 |
User & Date: | drh 2007-08-09 00:00:26.000 |
Context
2007-08-10
| ||
16:41 | Add the --soft-heap-limit=N option to the test scripts. Set this value to enforce a soft heap limit across all tests. This changes exposes several new bugs. (CVS 4202) (check-in: 8be8459816 user: drh tags: trunk) | |
2007-08-09
| ||
00:00 | Fix documentation typos. Tickets #2168 and #2560. (CVS 4201) (check-in: 4333b231af user: drh tags: trunk) | |
2007-08-08
| ||
12:11 | More tweaking of linkage. Ticket #2554. (CVS 4200) (check-in: 3759a38fe8 user: drh tags: trunk) | |
Changes
Changes to www/lang.tcl.
1 2 3 | # # Run this Tcl script to generate the lang-*.html files. # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this Tcl script to generate the lang-*.html files. # set rcsid {$Id: lang.tcl,v 1.133 2007/08/09 00:00:26 drh Exp $} source common.tcl if {[llength $argv]>0} { set outputdir [lindex $argv 0] } else { set outputdir "" } |
︙ | ︙ | |||
1077 1078 1079 1080 1081 1082 1083 | be encoded by putting two single quotes in a row - as in Pascal. C-style escapes using the backslash character are not supported because they are not standard SQL. BLOB literals are string literals containing hexadecimal data and preceded by a single "x" or "X" character. For example:</p> <blockquote><pre> | | | 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 | be encoded by putting two single quotes in a row - as in Pascal. C-style escapes using the backslash character are not supported because they are not standard SQL. BLOB literals are string literals containing hexadecimal data and preceded by a single "x" or "X" character. For example:</p> <blockquote><pre> X'53514C697465' </pre></blockquote> <p> A literal value can also be the token "NULL". </p> <p> |
︙ | ︙ | |||
1590 1591 1592 1593 1594 1595 1596 | puts { <p>The INSERT statement comes in two basic forms. The first form (with the "VALUES" keyword) creates a single new row in an existing table. If no column-list is specified then the number of values must be the same as the number of columns in the table. If a column-list is specified, then the number of values must match the number of specified columns. Columns of the table that do not appear in the | | | 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 | puts { <p>The INSERT statement comes in two basic forms. The first form (with the "VALUES" keyword) creates a single new row in an existing table. If no column-list is specified then the number of values must be the same as the number of columns in the table. If a column-list is specified, then the number of values must match the number of specified columns. Columns of the table that do not appear in the column list are filled with the default value, or with NULL if no default value is specified. </p> <p>The second form of the INSERT statement takes it data from a SELECT statement. The number of columns in the result of the SELECT must exactly match the number of columns in the table if no column list is specified, or it must match the number of columns |
︙ | ︙ |
Changes to www/limits.tcl.
1 2 3 | # # Run this script to generate the limits.html output file # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this script to generate the limits.html output file # set rcsid {$Id: limits.tcl,v 1.5 2007/08/09 00:00:26 drh Exp $} source common.tcl header {Implementation Limits For SQLite} puts { <h2>Limits In SQLite</h2> <p> "Limits" in the context of this article means sizes or |
︙ | ︙ | |||
23 24 25 26 27 28 29 | were not well defined. The policy was that if it would fit in memory and you could count it with a 32-bit integer, then it should work. </p> <p> Unfortunately, the no-limits policy has been shown to create | | | | 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 | were not well defined. The policy was that if it would fit in memory and you could count it with a 32-bit integer, then it should work. </p> <p> Unfortunately, the no-limits policy has been shown to create problems. Because the upper bounds were not well defined, they were not tested, and bugs (including possible security exploits) were often found when pushing SQLite to extremes. For this reason, newer versions of SQLite have well-defined limits and those limits are tested as part of the test suite. </p> <p> This article defines what the limits of SQLite are and how they |
︙ | ︙ |