SQLite version 3.4.0 is now available for download from the SQLite
website and from the back-up site:

   http://www.sqlite.org/
   http://www.hwaci.com/sw/sqlite/

Version 3.4.0 fixes two bugs which can cause database corruption.
Upgrading is recommended for all users.  If you are compelled to
continue using an older version of SQLite, then please at least
read the documentation on how to avoid hitting these bugs.  See

   http://www.sqlite.org/cvstrac/wiki?p=CorruptionFollowingBusyError
   http://www.sqlite.org/cvstrac/tktview?tn=2418

The consequences of hitting either of these bugs is severe, but
both bugs are obscure and relatively difficult to hit.  So the
impact on most applications is likely to be minimal.  Even so,
we think it is better to be safe than sorry and recommend that
everybody upgrade as soon as possible.

In addition to the critical bug fixes above, Version 3.4.0 also
includes explicit, well-defined, and tested upper bounds for many
properties of SQLite.  The new upper-bounds might cause some legacy
applications that use excessively large strings, tables, or SQL
statements to break unless the default upper-bounds are increased
using compile-time options.  This is the reason that the version
of the new release is 3.4.0 instead of 3.3.18.  For more information
about the new upper bounds, see

   http://www.sqlite.org/limits.html

Version 3.4.0 also includes support for new features such as:

   *  Incremental BLOB I/O
   *  The zeroblob() SQL function
   *  Incremental vacuum 

Additional information about these new features is available online.

By popular request, the preprocessed source code is now available
again as individual C code files.  The amalgamation is also still
available but has a different filename for downloading.

Do not be deceived by the ".0" at the end of the version number.
This release is one of the most extensively tested and debugged
releases of SQLite in a long time.  We expect it to be stable.
We will be more confident in that assertion after we have had some
additional real-world experience with it, but we are going into
this release with the expectation that it will prove to be 
production ready.  I will send follow-up messages to this list
if that expectation proves unfounded.  The key point is that 
version 3.4.0 is *not* a beta release.

As always, please report any issues that you find either to this
mailing list, to the SQLite ticket system, or directly to me and/or
Dan.

--
D. Richard Hipp <[EMAIL PROTECTED]>


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to