Documentation Source Text

  The two issues that prompted releases 3.6.9 and 3.6.10 were both
  discovered by internal testing and review - not by external users.
  And, indeed, most the problems found in SQLite these days are discovered
  by our rigorous <a href="testing.html">internal testing protocol</a>,
  not bug reports from the field.

  It has also been argued that we should withhold releases "until testing
  is finished."  The falacy there is that we never finish testing.  We
  are constantly writing new test cases for SQLite and thinking of new
  ways to stress and potentially break the code.  This is a continuous,
  never-ending, and on-going process.  All existing tests pass before each
  release.  But we will always be writing new tests the day after a release,
  regardless of how long we delay that release.  And sometimes those new
  tests will uncover new problems.

................................................................................
newsitem {2009-Jan-12} {Version 3.6.8} {
  SQLite [version 3.6.8] adds support for
  [SAVEPOINT | nested transactions] and improved optimization of
  WHERE clauses with
  <a href="optoverview.html#or_opt">OR-connected terms</a>.  There is also
  a new [SQLITE_ENABLE_FTS3_PARENTHESIS | compile-time option] that changes
  the way full-text search patterns are parsed so that they can contain
  nested paratheses.

  These are substantial changes.  Even so, the
  <a href="testing.html">release testing</a> for SQLite
  has become so extensive that the developers have high confidence that
  this release is stable and ready for production use.
}

................................................................................
newsitem {2008-Nov-22} {Version 3.6.6.1} {
  This release fixes a bug that was introduced into SQLite [version 3.6.4]
  and that can cause database corruption in obscure cases.  This bug has
  never been seen in the wild; it was first detected by internal stress
  tests and required substantial analysis before it could be shown to 
  potentially lead to corruption.  So we feel that SQLite versions 3.6.4,
  3.6.5, and 3.6.6 are safe to use for development work.  But upgrading
  to this patch release or later is recommented prior to deploying
  products that incorporate SQLite.

  We have taken the unusual step of issuing a patch release in order to
  get the fix for this bug into circulation quickly.  SQLite version 3.6.7
  will continue on its normal path of development with an anticipated
  release in mid December.  
}

  The two issues that prompted releases 3.6.9 and 3.6.10 were both
  discovered by internal testing and review - not by external users.
  And, indeed, most the problems found in SQLite these days are discovered
  by our rigorous <a href="testing.html">internal testing protocol</a>,
  not bug reports from the field.

  It has also been argued that we should withhold releases "until testing
  is finished."  The fallacy there is that we never finish testing.  We
  are constantly writing new test cases for SQLite and thinking of new
  ways to stress and potentially break the code.  This is a continuous,
  never-ending, and on-going process.  All existing tests pass before each
  release.  But we will always be writing new tests the day after a release,
  regardless of how long we delay that release.  And sometimes those new
  tests will uncover new problems.

................................................................................
newsitem {2009-Jan-12} {Version 3.6.8} {
  SQLite [version 3.6.8] adds support for
  [SAVEPOINT | nested transactions] and improved optimization of
  WHERE clauses with
  <a href="optoverview.html#or_opt">OR-connected terms</a>.  There is also
  a new [SQLITE_ENABLE_FTS3_PARENTHESIS | compile-time option] that changes
  the way full-text search patterns are parsed so that they can contain
  nested parentheses.

  These are substantial changes.  Even so, the
  <a href="testing.html">release testing</a> for SQLite
  has become so extensive that the developers have high confidence that
  this release is stable and ready for production use.
}

................................................................................
newsitem {2008-Nov-22} {Version 3.6.6.1} {
  This release fixes a bug that was introduced into SQLite [version 3.6.4]
  and that can cause database corruption in obscure cases.  This bug has
  never been seen in the wild; it was first detected by internal stress
  tests and required substantial analysis before it could be shown to 
  potentially lead to corruption.  So we feel that SQLite versions 3.6.4,
  3.6.5, and 3.6.6 are safe to use for development work.  But upgrading
  to this patch release or later is recommenced prior to deploying
  products that incorporate SQLite.

  We have taken the unusual step of issuing a patch release in order to
  get the fix for this bug into circulation quickly.  SQLite version 3.6.7
  will continue on its normal path of development with an anticipated
  release in mid December.  
}