Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Update documentation for the 3.7.6.1 patch release. Fix a typos in the FTS4 documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
0a742ee49aafa4660727d67fd60df132 |
User & Date: | drh 2011-04-13 18:37:49.670 |
Context
2011-04-17
| ||
18:03 | Update the website for version 3.7.6.2. (check-in: 773de3a641 user: drh tags: trunk) | |
2011-04-13
| ||
18:37 | Update documentation for the 3.7.6.1 patch release. Fix a typos in the FTS4 documentation. (check-in: 0a742ee49a user: drh tags: trunk) | |
2011-04-12
| ||
19:40 | Another typo in howtocorrupt.html (check-in: 0a0f9e093b user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
37 38 39 40 41 42 43 44 45 46 47 48 49 50 | <a href="http://www.sqlite.org/src/timeline"> http://www.sqlite.org/src/timeline</a>.</p> } hd_close_aux hd_enable_main 1 } } chng {2011 April 12 (3.7.6)} { <li> Added the [sqlite3_wal_checkpoint_v2()] interface and enhanced the [wal_checkpoint pragma] to support blocking checkpoints. <li> Improvements to the query planner so that it makes better estimates of plan costs and hence does a better job of choosing the right plan, especially when [SQLITE_ENABLE_STAT2] is used. | > > > > > > > > > > | 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 | <a href="http://www.sqlite.org/src/timeline"> http://www.sqlite.org/src/timeline</a>.</p> } hd_close_aux hd_enable_main 1 } } chng {2011 April 14 (3.7.6.1)} { <li> Fix a bug in 3.7.6 that only appears if the [SQLITE_FCNTL_SIZE_HINT] file control is used with a build of SQLite that makes use of the HAVE_POSIX_FALLOCATE compile-time option and which has SQLITE_ENABLE_LOCKING_MODE turned off. <li> SQLITE_SOURCE_ID: "2011-04-13 14:40:25 a35e83eac7b185f4d363d7fa51677f2fdfa27695" <li> SHA1 for sqlite3.c: b81bfa27d3e09caf3251475863b1ce6dd9f6ab66 } chng {2011 April 12 (3.7.6)} { <li> Added the [sqlite3_wal_checkpoint_v2()] interface and enhanced the [wal_checkpoint pragma] to support blocking checkpoints. <li> Improvements to the query planner so that it makes better estimates of plan costs and hence does a better job of choosing the right plan, especially when [SQLITE_ENABLE_STAT2] is used. |
︙ | ︙ |
Changes to pages/fts3.in.
︙ | ︙ | |||
210 211 212 213 214 215 216 | <tr><th>Option<th>Interpretation <tr><td>matchinfo<td> This option may only be set to the value "fts3". Attempting to set it otherwise is an error. If this option is specified, then some of the extra information stored by FTS4 is omitted. This reduces the amount of disk space consumed by an FTS4 table until it is almost the same as the amount that would be used by the equivalent FTS3 table, but also means that the data accessed by passing the 'l' flag to the | | | 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 | <tr><th>Option<th>Interpretation <tr><td>matchinfo<td> This option may only be set to the value "fts3". Attempting to set it otherwise is an error. If this option is specified, then some of the extra information stored by FTS4 is omitted. This reduces the amount of disk space consumed by an FTS4 table until it is almost the same as the amount that would be used by the equivalent FTS3 table, but also means that the data accessed by passing the 'l' flag to the [matchinfo()] function is not available. <tr><td>compress<td> This option is used to specify the compress function. It is an error to specify a compress function without also specifying an uncompress function. <tr><td>uncompress<td> |
︙ | ︙ | |||
1340 1341 1342 1343 1344 1345 1346 | <table striped=1> <tr><th>Column Name<th>Column Contents <tr><td>term<td> Contains the text of the term for this row. <tr><td>col<td> This column may contain either the text value '*' (i.e. a single character, UTF codepoint 42) or an integer between 0 and N-1, where N is | | | 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 | <table striped=1> <tr><th>Column Name<th>Column Contents <tr><td>term<td> Contains the text of the term for this row. <tr><td>col<td> This column may contain either the text value '*' (i.e. a single character, UTF codepoint 42) or an integer between 0 and N-1, where N is again the number of user-defined columns in the corresponding FTS table. <tr><td>documents<td> This column always contains an integer value greater than zero. <br><br> If the "col" column contains the value '*', then this column contains the number of rows of the FTS table that contain at least one instance of the term (in any column). If col contains an integer |
︙ | ︙ |
Changes to pages/howtocorrupt.in.
︙ | ︙ | |||
161 162 163 164 165 166 167 | will occasionally ask the operating system to flush all pending writes to persistent storage then wait for that flush to complete. This is accomplished using the <tt>fsync()</tt> system call under unix and <tt>FlushFileBuffers()</tt> under windows. We call this flush of pending writes a "sync".</p> <p>Actually, if one is only concerned with atomic and consistent writes and | | | 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 | will occasionally ask the operating system to flush all pending writes to persistent storage then wait for that flush to complete. This is accomplished using the <tt>fsync()</tt> system call under unix and <tt>FlushFileBuffers()</tt> under windows. We call this flush of pending writes a "sync".</p> <p>Actually, if one is only concerned with atomic and consistent writes and is willing to forego durable writes, the sync operation does not need to wait until the content is completely stored on persistent media. Instead, the sync operation can be thought of as an I/O barrier. As long as all writes that occur before the sync are completed before any write that happens after the sync, no database corruption will occur. If sync is operating as an I/O barrier and not as a true sync, then a power failure or system crash might cause one or more previously committed transactions to roll back (in violation of the "durable" property of "ACID") but the database will at |
︙ | ︙ | |||
339 340 341 342 343 344 345 | which could lead to database corruption if subsequent writes are attempted.</p> <p>Note that this problem only occurs if the attempt to acquire the lock resulted in an I/O error. If the lock is simply not granted (because some other thread or process is already holding a conflicting lock) then no corruption will ever occur. We are not aware of any operating systems that will fail with an I/O error while attempting to get a file lock on shared | | | 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 | which could lead to database corruption if subsequent writes are attempted.</p> <p>Note that this problem only occurs if the attempt to acquire the lock resulted in an I/O error. If the lock is simply not granted (because some other thread or process is already holding a conflicting lock) then no corruption will ever occur. We are not aware of any operating systems that will fail with an I/O error while attempting to get a file lock on shared memory. So this is a theoretical problem rather than a real problem. Needless to say, this problem has never been observed in the wild. The problem was discovered while doing stress testing of SQLite in a test harness that simulates I/O errors.</p> <p>This problem was fixed on 2010-09-20 for SQLite version 3.7.3.</p> <h3>7.4 Database pages leak from the free page list</h3> |
︙ | ︙ |
Changes to pages/index.in.
︙ | ︙ | |||
83 84 85 86 87 88 89 | </td> <td width="20"></td><td bgcolor="#044a64" width="1"></td><td width="20"></td> <td valign="top"> <h3>Current Status</h3> <p><ul> | | | | 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 | </td> <td width="20"></td><td bgcolor="#044a64" width="1"></td><td width="20"></td> <td valign="top"> <h3>Current Status</h3> <p><ul> <li><a href="releaselog/3_7_6_1.html">Version 3.7.6.1</a> of SQLite is recommended for all new development. Upgrading from version 3.7.5 or 3.7.6 is optional. Upgrading from all SQLite versions prior to 3.7.5 is recommended.</li> </ul></p> <h3>Common Links</h3> <p><ul> <li> <a href="features.html">Features</a> </li> |
︙ | ︙ |
Changes to pages/news.in.
︙ | ︙ | |||
14 15 16 17 18 19 20 21 22 23 24 25 26 27 | hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt regsub -all {[Tt]icket #(\d+)} $txt \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt hd_resolve "<p>$txt</p>" hd_puts "<hr width=\"50%\">" } newsitem {2011-April-12} {Version 3.7.6} { SQLite [version 3.7.6] is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.5 is optional. Upgrading releases prior to 3.7.5 is recommended. } | > > > > > > > > > > > | 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt regsub -all {[Tt]icket #(\d+)} $txt \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt hd_resolve "<p>$txt</p>" hd_puts "<hr width=\"50%\">" } newsitem {2011-April-13} {Version 3.7.6.1} { SQLite [version 3.7.6.1] fixes a single bug in 3.7.6 that can cause a segfault if [SQLITE_FCNTL_SIZE_HINT] is used on a unix build that has SQLITE_ENABLE_LOCKING_MODE set to 0 and is compiled with HAVE_POSIX_FALLOCATE. Upgrading from 3.7.6 is only needed for users effected by the configuration-specific bug described above. There are no other changes to the code. } newsitem {2011-April-12} {Version 3.7.6} { SQLite [version 3.7.6] is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.5 is optional. Upgrading releases prior to 3.7.5 is recommended. } |
︙ | ︙ |