Changes between Version 42 and Version 43 of PySqlite

Timestamp:

Sep 2, 2009, 1:30:48 PM (15 years ago)

Author:

Christian Boos

Comment:

some notes about upgrade from SQLite v2 to v3 databases being required for 0.12

PySqlite

@@ -61 +61 @@
    * version ''1.1.7'' required if using SQLite >= 3.3.3 
    But really, you should be using the 2.x versions, at this time.
-   Trac bug reports involving the obsolete pysqlite 1.0.x will simply not be considered.
  * or, '''better''', one of the newer 2.x release branch 
    * version >= 2.0.5 preferred, 
@@ -76 +75 @@
  * you need ''2.3.3'' if you use Apache and `mod_cache` (see Pysqlite:#174).
 
+Note that bug reports involving the obsolete pysqlite 1.0.x (for SQLite v2)
+will simply not be considered. Starting with 0.11.6, there will be an explicit
+deprecation warning and in 0.12, support for that version will be removed.
+
 ==== Downloading Pysqlite ====
 
@@ -86 +89 @@
 == Upgrading SQLite ==
 === Upgrading SQLite from 2.x to 3.x ===
+
+It is not advised anymore to use SQLite 2.x. Support for this version and the corresponding PySqlite 1.0.x bindings will be dropped in Trac version [milestone:0.12].
+If you happen to use that version, you will need to upgrade.
+
 The following information is copied from http://dev.ctor.org/pkcs1/wiki/TracUpgrade
 
@@ -180 +187 @@
 Otherwise, this is also a typical error seen when accessing a SQLite 2.x database file with a SQLite 3.x library.
 
-See [wiki:0.10/TracUpgrade#From0.8.xto0.9].
+See [#UpgradingSQLitefrom2.xto3.x above] for the upgrade instructions.
 
 ==== `OperationalError: SQL logic error or missing database` ====