Issue #3854: Documented using the sqlite3 module with multiple threads.
This commit is contained in:
parent
f045d775fd
commit
c34d76cdc3
|
@ -867,3 +867,18 @@ exception, the transaction is rolled back; otherwise, the transaction is
|
||||||
committed:
|
committed:
|
||||||
|
|
||||||
.. literalinclude:: ../includes/sqlite3/ctx_manager.py
|
.. literalinclude:: ../includes/sqlite3/ctx_manager.py
|
||||||
|
|
||||||
|
|
||||||
|
Common issues
|
||||||
|
-------------
|
||||||
|
|
||||||
|
Multithreading
|
||||||
|
^^^^^^^^^^^^^^
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
The only exception is calling the :meth:`~Connection.interrupt` method, which
|
||||||
|
only makes sense to call from a different thread.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue