summaryrefslogtreecommitdiff
path: root/doc/modules
diff options
context:
space:
mode:
authorRyan Williams <rdw@lindenlab.com>2010-02-21 11:45:13 -0500
committerRyan Williams <rdw@lindenlab.com>2010-02-21 11:45:13 -0500
commit533c8690ef114f0ec2cdcce763458a14b25bfefc (patch)
treeaa3c2048bad3ef5aefe1d9a0dd7fec6962545d24 /doc/modules
parent91709905df94c4c2bbf378dd5d2c69ab4c593e02 (diff)
downloadeventlet-533c8690ef114f0ec2cdcce763458a14b25bfefc.tar.gz
Doc tweaks.
Diffstat (limited to 'doc/modules')
-rw-r--r--doc/modules/db_pool.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/modules/db_pool.rst b/doc/modules/db_pool.rst
index 7a9d887..771dfbe 100644
--- a/doc/modules/db_pool.rst
+++ b/doc/modules/db_pool.rst
@@ -3,7 +3,7 @@
The db_pool module is useful for managing database connections. It provides three primary benefits: cooperative yielding during database operations, concurrency limiting to a database host, and connection reuse. db_pool is intended to be database-agnostic, compatible with any DB-API 2.0 database module.
-*Caveat: however, it has currently only been tested and used with MySQLdb.*
+*It has currently been tested and used with both MySQLdb and psycopg2.*
A ConnectionPool object represents a pool of connections open to a particular database. The arguments to the constructor include the database-software-specific module, the host name, and the credentials required for authentication. After construction, the ConnectionPool object decides when to create and sever connections with the target database.