Changes between Version 20 and Version 21 of PySqlite

Timestamp:

Oct 3, 2006, 9:34:51 AM (18 years ago)

Author:

Christian Boos

Comment:

Advise to use pysqlite 2.3.2 and other updates

PySqlite

@@ -11 +11 @@
 
 Trac 0.9 works best with '''[http://www.sqlite.org/version3.html SQLite 3.x]''', 
-like SQLite 3.2.8 or SQLite 3.3.x. 
+like SQLite 3.2.8 or SQLite 3.3.x (latest is 3.3.7).
 
 Pay attention to 
@@ -40 +40 @@
 === The Pysqlite2 bindings ===
 
-The most stable versions are '''2.0.7''' and '''2.1.3'''. 
-
-'''2.2.2''' is probably rock solid as well, as it has been
-extensively reviewed during its inclusion in Python 2.5.
-
-
-Detailed release information:
+The most stable version is now '''2.3.2'''.
+
+Detailed information about older releases:
  * either the 1.x release branch of PySqlite 
    * version 1.1.6 as of this writing,
@@ -57 +53 @@
    This release branch features a new statement cache and 
    a better handling of concurrent write operations.
- * the brand new ''2.2.0'' version appears to work with Trac as well
-   (I tested the 2.4 egg from initrd on Windows, and on Linux I 
+ * the ''2.2.0'' version appears to work with Trac as well
+   (I tested the 2.4 egg from initd on Windows, and on Linux I 
    built it from source, linking with sqlite-3.3.4; so far both 
    are working perfectly)
@@ -144 +140 @@
 request triggerd an attempted to write.
 There are probably a few things that could be enhanced in the
-future to handle this situation, like automatic retry (or improve
-the session code).
+future to handle this situation, like automatic retry, see #3446.
+
+Also, is this error is somehow inevitable with SQLite, we should make 
+the error message a bit more "user friendly" (#3503).
 
 The lock error is also much more frequent if SQLite is used in a 
 multi-threaded environment (like TracStandalone or TracModPython) 
 but the library was not compiled to be thread-safe. 
-See above [wiki:PySqlite#Buildingsqliteyourself building from source] 
-and #2170.
+See above, [#BuildingSQLiteyourself building from source], and #2170.
 
 The real problem with this occurs when ''all'' requests to Trac
@@ -165 +162 @@
    Upgrading Trac and Pysqlite will solve the issue (see #2345)
 
+See also: SQLite:DatabaseIsLocked.
+
 ==== `ProgrammingError: library routine called out of sequence` ====
 
 This happens on MacOS X, and is still an open issue (see #2969)
+
+See also: SQLite:LibraryRoutineCalledOutOfSequence.
 
 ==== `Warning: You can only execute one statement at a time.` ====
@@ -214 +215 @@
 ([http://projects.edgewall.com/trac/ticket/2170#change_8 details])
 
+Segmentation faults can also happen in multi-threaded servers using a SQLite library which has ''not'' been configured to be multi-thread safe (see [#BuildingSQLiteyourself above]).
 
 '''P.S. Note that despite of all of the above, for some (most?) users, SQLite/Pysqlite works flawlessly :)'''