Menu

Commit [r3756]  Maximize  Restore  History

Fix the logic of the !ConnectionPool w.r.t to threads.

!PooledConnection could end up being garbage collected in an other thread than the one which created it.
- this triggered an assertion (#3504)
- even if the assertion was avoided by properly tracking the !PooledConnection, with some backends (pysqlite) it's illegal to manipulate a Connection from a different thread than the one which created the instance.

Therefore we had to ensure that upon thread termination, the connection created and used by the thread was properly closed.

Closes #3504.

cboos 2006-09-20

changed /trunk/trac/db/api.py
changed /trunk/trac/db/pool.py
changed /trunk/trac/env.py
changed /trunk/trac/web/main.py
/trunk/trac/db/api.py Diff Switch to side-by-side view
Loading...
/trunk/trac/db/pool.py Diff Switch to side-by-side view
Loading...
/trunk/trac/env.py Diff Switch to side-by-side view
Loading...
/trunk/trac/web/main.py Diff Switch to side-by-side view
Loading...
MongoDB Logo MongoDB