FWIW, my understanding is that MySQL connections are quick to make and you don't gain much from pooling (at least if the server is on the same host as the client). So it might not be so bad to avoid pooling connections entirely. I know this isn't true for a lot of other databases, and I don't know much time Postgres connections take, but maybe other people have run their own experiments (e.g., running a thousand simple queries, once with a single connection and another time with new connections for each query).
During entirely unrelated browsing I came upon the Psycopg homepage, and noted that it does pooling as part of the driver, so DBPool or any other pooling of psycopg connections should not be necessary. I would presume that psycopg knows enough to get rid of bad connections in its internal pool.
So that covers the big two databases (at least the big two for me).
-- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
