Yes, we do just this (with Postgres) using DBPool, in order to share the same
connections for our SQLObject and non-SQLObject functionality. Just need to
override a few functions (we create the DBPools in a separate module that
handles creating one for DSNs we haven't seen yet on the fly. the
module-global variable _stores hands these out. You could put similar
functionality to create the pool into the Connection's code below if you
weren't sharing with non-SQLObject)
Can't speak for how DBPool compares to SQLObject's native pooling.
- Luke
------------> code
from SQLObject import PostgresConnection as PC
from PostgresPool import _stores
class PostgresConnection(PC):
def getConnection(self):
return _stores.getConnection(self.dsn)
def releaseConnection(self,conn):
conn.close()
def makeConnection(self):
pass
Quoting Frank Barknecht <fb...@fo...>:
> Hallo,
>
> when running an SQLObject-enhanced Webware application, is it possible
> and does it make sense, to "pool" the database connection the way,
> Webware's DBPool does? I'm expecially considering this for MySQL.
>
> ciao
> --
> Frank Barknecht _ ______footils.org__
>
|
