Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add documentation for the SQLITE_WIN32_HEAP compile-time option. Fix typos in the change log. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
907e8cfb736370f892ae759018f1d041 |
User & Date: | drh 2013-11-27 01:26:34.002 |
Context
2013-11-27
| ||
04:26 | Update the skip-scan documentation to mention the magic 18 number for when skip-scan becomes profitable. (check-in: 3eaa7f572e user: drh tags: trunk) | |
01:26 | Add documentation for the SQLITE_WIN32_HEAP compile-time option. Fix typos in the change log. (check-in: 907e8cfb73 user: drh tags: trunk) | |
2013-11-26
| ||
21:07 | Change the documented behavior of casting a large real into an integer. (check-in: f9d830d206 user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
15 16 17 18 19 20 21 | proc chng {date desc {options {}}} { global nChng aChng set aChng($nChng) [list $date $desc $options] incr nChng } chng {2013-12-10 (3.8.2)} { | | | | | | > | 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | proc chng {date desc {options {}}} { global nChng aChng set aChng($nChng) [list $date $desc $options] incr nChng } chng {2013-12-10 (3.8.2)} { <li>Changed the defined behavior for the [CAST expression] when floating point values greater than +9223372036854775807 are cast into into integers so that the result is the largest possible integer, +9223372036854775807, instead of the smallest possible integer, -9223372036854775808. After this change, CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead of -9223372036854775808. <b><big>←</big> Potentially Incompatible Change!</b> <li>Added support for [WITHOUT ROWID] tables. <li>Added the [skip-scan optimization] to the query planner. <li>Extended the [virtual table] interface, and in particular the [sqlite3_index_info] object to allow a virtual table to report its estimate on the number of rows that will be returned by a query. <li>Update the [R-Tree extension] to make use of the enhanced virtual table interface. |
︙ | ︙ |
Changes to pages/compile.in.
︙ | ︙ | |||
217 218 219 220 221 222 223 224 225 226 227 228 229 230 | Setting SQLITE_POWERSAFE_OVERWRITE to 1 causes SQLite to assume that application-level writes cannot changes bytes outside the range of bytes written even if the write occurs just before a power loss. With SQLITE_POWERSAFE_OVERWRITE set to 0, SQLite assumes that other bytes in the same sector with a written byte might be changed or damaged by a power loss. } COMPILE_OPTION {YYSTACKDEPTH=<i><max_depth></i>} { This macro sets the maximum depth of the LALR(1) stack used by the SQL parser within SQLite. The default value is 100. A typical application will use less than about 20 levels of the stack. Developers whose applications contain SQL statements that need more than 100 LALR(1) stack entries should seriously | > > > > > | 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 | Setting SQLITE_POWERSAFE_OVERWRITE to 1 causes SQLite to assume that application-level writes cannot changes bytes outside the range of bytes written even if the write occurs just before a power loss. With SQLITE_POWERSAFE_OVERWRITE set to 0, SQLite assumes that other bytes in the same sector with a written byte might be changed or damaged by a power loss. } COMPILE_OPTION {SQLITE_WIN32_MALLOC} { This option enables the use of the Windows Heap API functions for memory allocation instead of the standard library malloc() and free() routines. } COMPILE_OPTION {YYSTACKDEPTH=<i><max_depth></i>} { This macro sets the maximum depth of the LALR(1) stack used by the SQL parser within SQLite. The default value is 100. A typical application will use less than about 20 levels of the stack. Developers whose applications contain SQL statements that need more than 100 LALR(1) stack entries should seriously |
︙ | ︙ |