Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| SHA1 Hash: | 8a8b9f4250845c42d8dce6c82f9b106c48b13d82 |
|---|---|
| Date: | 2013-03-09 15:12:39 |
| User: | drh |
| Comment: | Fix various documentation typos. |
Tags And Properties
- branch=trunk inherited from [b2e03e19ab]
- sym-trunk inherited from [b2e03e19ab]
Changes
Changes to pages/books.in
13 Publisher: Apress<br> 13 Publisher: Apress<br> 14 <a href="http://www.amazon.com/gp/product/1430232250">Amazon</a></p> 14 <a href="http://www.amazon.com/gp/product/1430232250">Amazon</a></p> 15 15 16 <p> 16 <p> 17 Outside of the world of enterprise computing, there is one database 17 Outside of the world of enterprise computing, there is one database 18 that enables a huge range of software and hardware to flex relational 18 that enables a huge range of software and hardware to flex relational 19 database capabilities, without the baggage and cost of traditional 19 database capabilities, without the baggage and cost of traditional 20 database management systems. That database is SQLite\u2014an embeddable | 20 database management systems. That database is SQLite - an embeddable 21 database with an amazingly small footprint, yet able to handle databases 21 database with an amazingly small footprint, yet able to handle databases 22 of enormous size. SQLite comes equipped with an array of powerful 22 of enormous size. SQLite comes equipped with an array of powerful 23 features available through a host of programming and development 23 features available through a host of programming and development 24 environments. It is supported by languages such as C, Java, Perl, 24 environments. It is supported by languages such as C, Java, Perl, 25 PHP, Python, Ruby, TCL, and more.</p> 25 PHP, Python, Ruby, TCL, and more.</p> 26 26 27 <p><i>The Definitive Guide to SQLite, Second Edition</i> 27 <p><i>The Definitive Guide to SQLite, Second Edition</i>
Changes to pages/faq.in
46 46 47 <p>Note that the integer key is one greater than the largest 47 <p>Note that the integer key is one greater than the largest 48 key that was in the table just prior to the insert. The new key 48 key that was in the table just prior to the insert. The new key 49 will be unique over all keys currently in the table, but it might 49 will be unique over all keys currently in the table, but it might 50 overlap with keys that have been previously deleted from the 50 overlap with keys that have been previously deleted from the 51 table. To create keys that are unique over the lifetime of the 51 table. To create keys that are unique over the lifetime of the 52 table, add the [AUTOINCREMENT] keyword to the [INTEGER PRIMARY KEY] 52 table, add the [AUTOINCREMENT] keyword to the [INTEGER PRIMARY KEY] 53 declaration. Then the key chosen will be one more than than the | 53 declaration. Then the key chosen will be one more than the 54 largest key that has ever existed in that table. If the largest 54 largest key that has ever existed in that table. If the largest 55 possible key has previously existed in that table, then the [INSERT] 55 possible key has previously existed in that table, then the [INSERT] 56 will fail with an [SQLITE_FULL] error code.</p> 56 will fail with an [SQLITE_FULL] error code.</p> 57 } 57 } 58 58 59 faq { 59 faq { 60 What datatypes does SQLite support? 60 What datatypes does SQLite support? ................................................................................................................................................................................ 357 <p>An [SQLITE_SCHEMA] error is returned when a 357 <p>An [SQLITE_SCHEMA] error is returned when a 358 prepared SQL statement is no longer valid and cannot be executed. 358 prepared SQL statement is no longer valid and cannot be executed. 359 When this occurs, the statement must be recompiled from SQL using 359 When this occurs, the statement must be recompiled from SQL using 360 the [sqlite3_prepare()] API. 360 the [sqlite3_prepare()] API. 361 An SQLITE_SCHEMA error can only occur when using the [sqlite3_prepare()], 361 An SQLITE_SCHEMA error can only occur when using the [sqlite3_prepare()], 362 and [sqlite3_step()] interfaces to run SQL. 362 and [sqlite3_step()] interfaces to run SQL. 363 You will never receive an [SQLITE_SCHEMA] error from 363 You will never receive an [SQLITE_SCHEMA] error from 364 [sqlite3_exec()]. Nor will you receive a the error if you | 364 [sqlite3_exec()]. Nor will you receive an error if you 365 prepare statements using [sqlite3_prepare_v2()] instead of 365 prepare statements using [sqlite3_prepare_v2()] instead of 366 [sqlite3_prepare()].</p> 366 [sqlite3_prepare()].</p> 367 367 368 <p>The [sqlite3_prepare_v2()] interface creates a 368 <p>The [sqlite3_prepare_v2()] interface creates a 369 [prepared statement] that will automatically recompile itself if 369 [prepared statement] that will automatically recompile itself if 370 the schema changes. The easiest way to deal with 370 the schema changes. The easiest way to deal with 371 [SQLITE_SCHEMA] errors is to always use [sqlite3_prepare_v2()] 371 [SQLITE_SCHEMA] errors is to always use [sqlite3_prepare_v2()]
Changes to pages/malloc.in
491 reducing memory requirements. This is particularly important for the 491 reducing memory requirements. This is particularly important for the 492 page cache memory since the page cache constitutes the largest component 492 page cache memory since the page cache constitutes the largest component 493 of the memory needs of SQLite. 493 of the memory needs of SQLite. 494 </p></li> 494 </p></li> 495 </ul> 495 </ul> 496 496 497 <p>The page-cache memory allocator is disabled by default. 497 <p>The page-cache memory allocator is disabled by default. 498 An application can enabled it at start-time as follows:</p> | 498 An application can enable it at start-time as follows:</p> 499 499 500 <blockquote><pre> 500 <blockquote><pre> 501 [sqlite3_config]([SQLITE_CONFIG_PAGECACHE], pBuf, sz, N); 501 [sqlite3_config]([SQLITE_CONFIG_PAGECACHE], pBuf, sz, N); 502 </pre></blockquote> 502 </pre></blockquote> 503 503 504 <p>The pBuf parameter is a pointer to a contiguous range of bytes that 504 <p>The pBuf parameter is a pointer to a contiguous range of bytes that 505 SQLite will use for page-cache memory allocations. The buffer must be 505 SQLite will use for page-cache memory allocations. The buffer must be
Changes to pages/vtab.in
49 file 49 file 50 <li> Access to the filesystem of the host computer 50 <li> Access to the filesystem of the host computer 51 <li> Enabling SQL manipulation of data in statistics packages like R 51 <li> Enabling SQL manipulation of data in statistics packages like R 52 </ul> 52 </ul> 53 53 54 <h3>1.1 Usage</h3> 54 <h3>1.1 Usage</h3> 55 55 56 <p>A virtual table is created using using a [CREATE VIRTUAL TABLE] statement. | 56 <p>A virtual table is created using a [CREATE VIRTUAL TABLE] statement. 57 This statement creates a table with a particular name and associates the 57 This statement creates a table with a particular name and associates the 58 table with a "module". 58 table with a "module". 59 59 60 <blockquote><pre> 60 <blockquote><pre> 61 CREATE VIRTUAL TABLE tablename USING modulename; 61 CREATE VIRTUAL TABLE tablename USING modulename; 62 </pre></blockquote> 62 </pre></blockquote> 63 63