Changes between Version 2 and Version 3 of PySqlite

Timestamp:

Nov 16, 2005, 9:23:05 AM (18 years ago)

Author:

Christian Boos

Comment:

Insist on the need to use a SQLite built with the --enable-threadsafe option

PySqlite

@@ -5 +5 @@
 which is Trac's default DatabaseBackend.
 
-Currently Trac works best with SQLite 3 and the compatible bindings are:
+It should still be possible to use the old SQLite 2.8.x
+with the Pysqlite [http://initd.org/pub/software/pysqlite/releases/1.0/1.0.1 1.0.1],
+but Trac 0.9 works best with '''SQLite 3.2.x'''. The compatible 
+Python bindings are:
  * either the 1.x release branch of PySqlite (version 1.1.6 as of this writing)
- * or the newer 2.0.x release branch (version >= 2.0.5 preferred)
+ * or, better, the newer 2.0.x release branch 
+   (version >= 2.0.5 preferred)
  * ''(the upcoming 2.1.x release branch has just been started and has not yet
    been tested with Trac)''
 
-Recent versions available from
+Recent versions are available from
 [http://initd.org/tracker/pysqlite/wiki#Downloads there].
 
-''Note: It should still be possible to use the old SQLite 2.8.x
-with the Pysqlite [http://initd.org/pub/software/pysqlite/releases/1.0/1.0.1 1.0.1].''
+
+'''Note:''' If you want to use Trac in a multi-threaded setup
+by using either TracModPython or TracStandalone, be sure to build a
+'''thread-safe version of SQLite''', by using the `--enable-threadsafe` 
+configuration switch.
+If you use a non thread-safe library, which is unfortunately what you
+get by default on non-windows platforms, you face the risk to get 
+persistent database locks (see #2170).