Browse files

Removed docs about cominbing pysqlite and apsw. This was experimental…

… and I don't want to support it.

Added note about using pysqlite in a multithreaded context.
  • Loading branch information...
ghaering committed Aug 6, 2010
1 parent 35f5d46 commit 2be0aeacc08961d95e0438dcd852909a56195f47
Showing with 9 additions and 13 deletions.
  1. +9 −13 doc/sphinx/sqlite3.rst
@@ -871,20 +871,16 @@ committed:
.. literalinclude:: ../includes/sqlite3/
-Combining APSW and pysqlite
+Common issues
-APSW is "Another Python SQLite Wrapper". Its goal is to directly wrap the
-SQLite API for Python. If there's SQLite functionality that is only wrapped via
-APSW, but not (yet) via pysqlite, then you can still use the APSW functionality
-in pysqlite.
-Just use the APSW Connection as a parameter to the connect function and reuse
-an existing APSW connection like this.
+Older SQLite versions had issues with sharing connections between threads.
+That's why the Python module disallows sharing connections and cursors between
+threads. If you still try to do so, you will get an exception at runtime.
-.. literalinclude:: ../includes/sqlite3/
-This feature only works if both APSW and pysqlite are dynamically linked
-against the same SQLite shared library. I. e. it will *not* work on Windows
-without a custom built pysqlite and APSW.
+The only exception is calling the :meth:`~Connection.interrupt` method, which
+only makes sense to call from a different thread.

0 comments on commit 2be0aea

Please sign in to comment.