Re: [Zope-dev] DA Question...
Hello,
I'm planning to write a product which depends on RDBMS access.
My only concern are those thread-issues... Could a connectionpool (an object that holds 10 or more open connections) be a way around this ?
What are you trying to solve? Either you can thread, or you can't. If you can't handle access from multiple threads, then 100 connections to the database are useless when you can only talk to one SQLMethod at a time. Connection pooling isn't that easy to get right either. Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com
Are there not DB client libraries which do not safely allow multiple threads accessing a single connection, but which would be perfectly happy if each thread drew a different connection from a pool? I believe InterBase (at least) works this way, and I suspect PostgreSQL of similar failings. ----- Original Message ----- From: Christopher Petrilli <petrilli@digicool.com>
What are you trying to solve? Either you can thread, or you can't. If you can't handle access from multiple threads, then 100 connections to the database are useless when you can only talk to one SQLMethod at a time.
On Tue, Aug 31, 1999 at 09:18:13AM -0500, Evan Simpson wrote:
Are there not DB client libraries which do not safely allow multiple threads accessing a single connection, but which would be perfectly happy if each thread drew a different connection from a pool? I believe InterBase (at least) works this way, and I suspect PostgreSQL of similar failings.
Thats the problem I want to solve. I feel a little bit funny about 10+ threads sharing the same connection. By using a connectionpool every thread get his own connection and established but not used connections could be "recycled". Sascha -- .-> Sascha Matzke - sascha@bespin.de - http://www.bespin.de -. | Keine Macht fuer niemand... | | Ton Steine Scherben | `-- On this earth for 23 years, 322 days <----------------'
participants (3)
-
Christopher Petrilli -
Evan Simpson -
Sascha Matzke