Edgewall Software

Changes between Version 2 and Version 3 of PySqlite


Ignore:
Timestamp:
Nov 16, 2005, 9:23:05 AM (17 years ago)
Author:
Christian Boos
Comment:

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

Legend:

Unmodified
Added
Removed
Modified
  • PySqlite

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