Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| SHA1 Hash: | 50fc706041b294c333fe37bf6757a543730b280a |
|---|---|
| Date: | 2012-12-03 20:10:10 |
| User: | drh |
| Comment: | Tweaks to the change log in preparation for 3.7.15. |
Tags And Properties
- branch=trunk inherited from [b2e03e19ab]
- sym-trunk inherited from [b2e03e19ab]
Changes
Changes to pages/asyncvfs.in
1 <title>An Asynchronous I/O Module For SQLite</title> 1 <title>An Asynchronous I/O Module For SQLite</title> 2 <tcl>hd_keywords {asynchronous VFS} {asynchronous I/O backend}</tcl> 2 <tcl>hd_keywords {asynchronous VFS} {asynchronous I/O backend}</tcl> 3 <h1 align="center">An Asynchronous I/O Module For SQLite</h1> 3 <h1 align="center">An Asynchronous I/O Module For SQLite</h1> 4 4 > 5 <hr> > 6 <p><font size=+1><b>NOTE:</b> > 7 [WAL mode] with [PRAGMA synchronous] set to NORMAL avoids calls to > 8 fsync() during transaction commit and only invokes fsync() during > 9 a [checkpoint] operation. The use of [WAL mode] largely obviates the > 10 need for this asynchronous I/O module. Hence, this module is no longer > 11 supported. The source code continues to exist in the SQLite source tree, > 12 but it is not a part of any standard build and is no longer maintained. > 13 This documentation is retained for historical reference.</font></p><hr> > 14 5 <p>Normally, when SQLite writes to a database file, it waits until the write 15 <p>Normally, when SQLite writes to a database file, it waits until the write 6 operation is finished before returning control to the calling application. 16 operation is finished before returning control to the calling application. 7 Since writing to the file-system is usually very slow compared with CPU 17 Since writing to the file-system is usually very slow compared with CPU 8 bound operations, this can be a performance bottleneck. The asynchronous I/O 18 bound operations, this can be a performance bottleneck. The asynchronous I/O 9 backend is an extension that causes SQLite to perform all write requests 19 backend is an extension that causes SQLite to perform all write requests 10 using a separate thread running in the background. Although this does not 20 using a separate thread running in the background. Although this does not 11 reduce the overall system resources (CPU, disk bandwidth etc.), it does 21 reduce the overall system resources (CPU, disk bandwidth etc.), it does
Changes to pages/changes.in
60 <li>Enhancements the command-line shell: 60 <li>Enhancements the command-line shell: 61 <ul> 61 <ul> 62 <li>Added the ".print" command 62 <li>Added the ".print" command 63 <li>Negative numbers in the ".width" command cause right-alignment 63 <li>Negative numbers in the ".width" command cause right-alignment 64 <li>Add the ".wheretrace" command when compiled with SQLITE_DEBUG 64 <li>Add the ".wheretrace" command when compiled with SQLITE_DEBUG 65 </ul> 65 </ul> 66 <li>Added the [busy_timeout pragma]. 66 <li>Added the [busy_timeout pragma]. > 67 <li>Added the [instr()] SQL function. 67 <li>Added the [SQLITE_FCNTL_BUSYHANDLER] file control, used to allow VFS 68 <li>Added the [SQLITE_FCNTL_BUSYHANDLER] file control, used to allow VFS 68 implementations to get access to the busy handler callback. 69 implementations to get access to the busy handler callback. > 70 <li>The xDelete method in the built-in [VFS | VFSes] now return > 71 SQLITE_IOERR_DELETE_NOENT if the file to be deleted does not exist. 69 <li>Enhanced support for QNX. 72 <li>Enhanced support for QNX. 70 <li>Work around an optimizer bug in the MSVC compiler when targeting ARM. 73 <li>Work around an optimizer bug in the MSVC compiler when targeting ARM. 71 <li>Fix various concurrency problems in shared-cache mode. 74 <li>Fix various concurrency problems in shared-cache mode. 72 <li>Bug fix: Avoid a deadlock or crash if the [backup API], [shared cache], 75 <li>Bug fix: Avoid a deadlock or crash if the [backup API], [shared cache], 73 and the SQLite Encryption Extension are all used at once. 76 and the SQLite Encryption Extension are all used at once. 74 <li>Bug fix: SQL functions created using the TCL interface honor the 77 <li>Bug fix: SQL functions created using the TCL interface honor the 75 "nullvalue" setting. 78 "nullvalue" setting.
Changes to pages/lang.in
2072 } 2072 } 2073 2073 2074 funcdef {ifnull(X,Y)} {} { 2074 funcdef {ifnull(X,Y)} {} { 2075 ^The ifnull() function returns a copy of its first non-NULL argument, or 2075 ^The ifnull() function returns a copy of its first non-NULL argument, or 2076 NULL if both arguments are NULL. ^Ifnull() must have exactly 2 arguments. 2076 NULL if both arguments are NULL. ^Ifnull() must have exactly 2 arguments. 2077 ^The ifnull() function is equivalent to [coalesce()] with two arguments. 2077 ^The ifnull() function is equivalent to [coalesce()] with two arguments. 2078 } 2078 } > 2079 > 2080 funcdef {instr(X,Y)} {} { > 2081 ^The instr(X,Y) function finds the first occurrence of string X within > 2082 string Y and returns the number of prior characters plus 1, or 0 if > 2083 X is nowhere found within Y. > 2084 ^Or, if X and Y are both BLOBs, then instr(X,Y) returns one > 2085 more than the number bytes prior to the first occurrence of X, or 0 if > 2086 X does not occcur anywhere within Y. > 2087 ^If both arguments X and Y to instr(X,Y) are non-NULL and are not BLOBs > 2088 then both are interpreted as strings. > 2089 ^If either X or Y are NULL in instr(X,Y) then the result is NULL. > 2090 } 2079 2091 2080 funcdef {hex(X)} {} { 2092 funcdef {hex(X)} {} { 2081 ^The hex() function interprets its argument as a BLOB and returns 2093 ^The hex() function interprets its argument as a BLOB and returns 2082 a string which is the upper-case hexadecimal rendering of the content of 2094 a string which is the upper-case hexadecimal rendering of the content of 2083 that blob. 2095 that blob. 2084 } 2096 } 2085 2097