Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | More documentation changes prior to the 3.5.0 alpha release. (CVS 4390) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
b15b03dfd6baef696c80ba1621cd36b1 |
User & Date: | drh 2007-09-04 01:58:27.000 |
Context
2007-09-04
| ||
02:38 | Version 3.5.0 Alpha (CVS 4391) (check-in: 1b690be22a user: drh tags: trunk) | |
01:58 | More documentation changes prior to the 3.5.0 alpha release. (CVS 4390) (check-in: b15b03dfd6 user: drh tags: trunk) | |
01:25 | Fix the malloc-10 test in malloc.test so that it will run on windows when invoked from exclusive3.test. (CVS 4389) (check-in: 1166f9c7d1 user: drh tags: trunk) | |
Changes
Changes to www/changes.tcl.
︙ | ︙ | |||
25 26 27 28 29 30 31 | regsub -all {[Tt]icket #(\d+)} $desc \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} desc puts "<DD><P><UL>$desc</UL></P>" puts "</DD>" } | | | 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 | regsub -all {[Tt]icket #(\d+)} $desc \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} desc puts "<DD><P><UL>$desc</UL></P>" puts "</DD>" } chng {2007 Sep 04 (3.5.0) alpha} { <li>Redesign the OS interface layer. See <a href="34to35.html">34to35.html</a> for details. <font color="red">*** Potentially incompatible change ***</font> <li>The <a href="capi3ref.html#sqlite3_release_memory"> sqlite3_release_memory()</a>, <a href="capi3ref.html#sqlite3_soft_heap_limit"> sqlite3_soft_heap_limit()</a>, |
︙ | ︙ |
Changes to www/faq.tcl.
1 2 3 | # # Run this script to generated a faq.html output file # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this script to generated a faq.html output file # set rcsid {$Id: faq.tcl,v 1.40 2007/09/04 01:58:27 drh Exp $} source common.tcl header {SQLite Frequently Asked Questions</title>} set cnt 1 proc faq {question answer} { set ::faq($::cnt) [list [string trim $question] [string trim $answer]] incr ::cnt |
︙ | ︙ | |||
159 160 161 162 163 164 165 | API functions.</p> } faq { Is SQLite threadsafe? } { <p>Yes. Sometimes. In order to be thread-safe, SQLite must be compiled | | < < | | | < < | | | | 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 | API functions.</p> } faq { Is SQLite threadsafe? } { <p>Yes. Sometimes. In order to be thread-safe, SQLite must be compiled with the SQLITE_THREADSAFE preprocessor macro set to 1. Both the windows and linux precompiled binaries in the distribution are compiled this way. If you are unsure if the SQLite library you are linking against is compiled to be threadsafe you can call the <a href="capi3ref.html#sqlite3_threadsafe">sqlite3_threadsafe()</a> interface to find out. </p> <p>Prior to version 3.3.1, an <b>sqlite3</b> structure could only be used in the same thread that called <a href="capi3ref.html#sqlite3_open">sqlite3_open</a> to create it. You could not open a database in one thread then pass the handle off to another thread for |
︙ | ︙ | |||
191 192 193 194 195 196 197 | <p>The restriction on moving database connections across threads was relaxed somewhat in version 3.3.1. With that and subsequent versions, it is safe to move a connection handle across threads as long as the connection is not holding any fcntl() locks. You can safely assume that no locks are being held if no transaction is pending and all statements have been finalized.</p> | < < < < < < < < < < < | 187 188 189 190 191 192 193 194 195 196 197 198 199 200 | <p>The restriction on moving database connections across threads was relaxed somewhat in version 3.3.1. With that and subsequent versions, it is safe to move a connection handle across threads as long as the connection is not holding any fcntl() locks. You can safely assume that no locks are being held if no transaction is pending and all statements have been finalized.</p> <p>Under UNIX, you should not carry an open SQLite database across a fork() system call into the child process. Problems will result if you do.</p> } faq { How do I list all tables/indices contained in an SQLite database |
︙ | ︙ |
Changes to www/index.tcl.
︙ | ︙ | |||
67 68 69 70 71 72 73 | proc newsitem {date title text} { puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt puts "<p>$txt</p>" puts "<hr width=\"50%\">" } | | | | 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 | proc newsitem {date title text} { puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt puts "<p>$txt</p>" puts "<hr width=\"50%\">" } newsitem {2007-Sep-04} {Version 3.5.0 alpha} { The OS interface layer and the memory allocation subsystems in SQLite have been reimplemented. The published API is largely unchanged but the (unpublished) OS interface has been modified extensively. Application that implement their own OS interface will require modification. See <a href="34to35.html">34to35.html</a> for details.<p> This is a large change approximately 1 line of count of out 10 was modified. We are calling this first release "alpha" in order to give the user community time to test and evaluate the changes before we freeze the new design. } newsitem {2007-Aug-13} {Version 3.4.2} { While stress-testing the <a href="capi3ref.html#sqlite3_soft_heap_limit">soft_heap_limit</a> |
︙ | ︙ | |||
105 106 107 108 109 110 111 | database corruption</a>. The bug was introduced in version <a href="changes.html#version_3_3_14">3.3.14</a>. Upgrading is recommended for all users. Also included are a slew of other more routine <a href="changes.html#version_3_4_1">enhancements and bug fixes</a>. } | < < < < < < < < < < < < < < < < < < < < < < < < < < | | 105 106 107 108 109 110 111 112 113 114 115 116 | database corruption</a>. The bug was introduced in version <a href="changes.html#version_3_3_14">3.3.14</a>. Upgrading is recommended for all users. Also included are a slew of other more routine <a href="changes.html#version_3_4_1">enhancements and bug fixes</a>. } puts { <p align="right"><a href="oldnews.html">Old news...</a></p> </td></tr></table> } footer {$Id: index.tcl,v 1.161 2007/09/04 01:58:27 drh Exp $} |
Changes to www/oldnews.tcl.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | #!/usr/bin/tclsh source common.tcl header {SQLite Older News} proc newsitem {date title text} { puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt puts "<p>$txt</p>" puts "<hr width=\"50%\">" } newsitem {2007-Apr-25} {Version 3.3.17} { This version fixes a bug in the forwards-compatibility logic of SQLite that was causing a database to become unreadable when it should have been read-only. Upgrade from 3.3.16 only if you plan to deploy into a product that might need to be upgraded in the future. For day to day use, it probably does not matter. | > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 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 39 40 41 42 43 | #!/usr/bin/tclsh source common.tcl header {SQLite Older News} proc newsitem {date title text} { puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt puts "<p>$txt</p>" puts "<hr width=\"50%\">" } newsitem {2007-Jun-18} {Version 3.4.0} { This release fixes two separate bugs either of which can lead to database corruption. Upgrading is strongly recommended. If you must continue using an older version of SQLite, please at least read about how to avoid these bugs at <a href="http://www.sqlite.org/cvstrac/wiki?p=CorruptionFollowingBusyError"> CorruptionFollowingBusyError</a> and <a href="http://www.sqlite.org/cvstrac/tktview?tn=2418">ticket #2418</a> <p> This release also adds explicit <a href="limits.html">limits</a> on the sizes and quantities of things SQLite will handle. The new limits might causes compatibility problems for existing applications that use excessively large strings, BLOBs, tables, or SQL statements. The new limits can be increased at compile-time to work around any problems that arise. Nevertheless, the version number of this release is 3.4.0 instead of 3.3.18 in order to call attention to the possible incompatibility. </p> There are also new features, including <a href="capi3ref.html#sqlite3_blob_open">incremental BLOB I/O</a> and <a href="pragma.html#pragma_incremental_vacuum">incremental vacuum</a>. See the <a href="changes.html#version_3_4_0">change log</a> for additional information. } newsitem {2007-Apr-25} {Version 3.3.17} { This version fixes a bug in the forwards-compatibility logic of SQLite that was causing a database to become unreadable when it should have been read-only. Upgrade from 3.3.16 only if you plan to deploy into a product that might need to be upgraded in the future. For day to day use, it probably does not matter. |
︙ | ︙ | |||
453 454 455 456 457 458 459 | changes to both the C-language API and the underlying file format that will enable SQLite to better support internationalization. The first beta is schedule for release on 2004-July-01. Plans are to continue to support SQLite version 2.8 with bug fixes. But all new development will occur in version 3.0. } | | | 478 479 480 481 482 483 484 485 | changes to both the C-language API and the underlying file format that will enable SQLite to better support internationalization. The first beta is schedule for release on 2004-July-01. Plans are to continue to support SQLite version 2.8 with bug fixes. But all new development will occur in version 3.0. } footer {$Id: oldnews.tcl,v 1.23 2007/09/04 01:58:27 drh Exp $} |