Changes between Version 16 and Version 17 of PySqlite

Timestamp:

May 5, 2006, 1:41:13 PM (18 years ago)

Author:

Christian Boos

Comment:

added page outline

PySqlite

@@ -1 +1 @@
 = PySqlite =
+
+[[PageOutline(2-3)]]
 
 [http://initd.org/tracker/pysqlite PySqlite] is a Python binding 
@@ -102 +104 @@
 also happen to you.
 
-=== `OperationalError: unsupported file format` ===
+=== Common ''Oops'' ===
+
+==== `OperationalError: unsupported file format` ====
 
   ''This probably is symptomatic of a mismatch between the SQLite library and the SQLite database format.''
@@ -108 +112 @@
 See Trac-ML:7540
 
-=== `OperationalError: SQL logic error or missing database` ===
+==== `OperationalError: SQL logic error or missing database` ====
 
   ''This can indicate that the database was corrupted.''
@@ -124 +128 @@
 And this ''might'' correspond to an open bug. See #2902 and #2570.
 
-=== `OperationalError: database is locked` ===
+==== `OperationalError: database is locked` ====
 
 There are numerous reasons why you can get this.
@@ -155 +159 @@
    Upgrading Trac and Pysqlite will solve the issue (see #2345)
 
-=== `ProgrammingError: library routine called out of sequence` ===
+==== `ProgrammingError: library routine called out of sequence` ====
 
 This happens on MacOS X, and is still an open issue (see #2969)
 
-=== `Warning: You can only execute one statement at a time.` ===
+==== `Warning: You can only execute one statement at a time.` ====
 
 This is typically an error which happens when the pysqlite package 
@@ -166 +170 @@
 (e.g. see #2993).
 
-=== `Segmentation Fault` ===
+
+=== Other issues ===
+
+==== `Segmentation Fault` ====
 
 Some old Python 2.3 versions (like on SuSE 9.0) have a bug