diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2006-05-29 16:49:42 +0000 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2006-05-29 16:49:42 +0000 |
| commit | 11fab37133fd2ae155179d64079965f307b4d57c (patch) | |
| tree | 880067eea1499351e44412fb8fa2a2b7d70a1e79 /doc | |
| parent | 0f4f7fd620d43dfbe263e8d1caf62ece2f625483 (diff) | |
| download | sqlalchemy-11fab37133fd2ae155179d64079965f307b4d57c.tar.gz | |
echo_pool flag fixed
removed incorrect paragraph regarding release modes
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/build/content/dbengine.txt | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/build/content/dbengine.txt b/doc/build/content/dbengine.txt index 85767bf14..2193ab6b5 100644 --- a/doc/build/content/dbengine.txt +++ b/doc/build/content/dbengine.txt @@ -181,8 +181,6 @@ The `threadlocal` strategy is better suited to a programming style which relies # are returned to the pool. r2 = None -While the `close()` method is still available with the "threadlocal" strategy, it should be used carefully. Above, if we issued a `close()` call on `r1`, and then tried to further work with results from `r2`, `r2` would be in an invalid state since its connection was already returned to the pool. By relying on `__del__()` to automatically clean up resources, this condition will never occur. - Advantages to `threadlocal` include that resources can be left to clean up after themselves, application code can be more minimal, its guaranteed that only one connection is used per thread, and there is no chance of a "connection pool block", which is when an execution hangs because the current thread has already checked out all remaining resources. To get at the actual `Connection` object which is used by implicit executions, call the `contextual_connection()` method on `Engine`: |