Re: database connection pooling

"Charl P. Botha" <[email protected]> Tue, 6 Sep 2005 20:50:42 +0200
Newsgroups gmane.comp.web.skunkweb
Message-ID <[email protected]>
Thank you very much for your detailed answer Jacob!

On 9/6/05, Jacob Smullyan <[email protected]> wrote:
> But the normal SkunkWeb approach is to keep one db connection around
> per process.  There are connection caching services in the skunkweb
> distribution for oracle, postgresql, and mysql.  I have never used the
> oracle service; it uses DCOracle, so if you want to use cx_oracle
> you'll need to modify/clone it.

I'll definitely look at doing this on the longer term, first I have to
have a look at the services code.

What I've done for now, partly because I'm using cx_Oracle, is to
setup a connection instance at module-level in one of the modules
imported by a component.  This leads to one instance per SkunkWeb
process as well.  It's not as nice as the SkunkWeb database services,
but I'll look into that a bit later.

Thanks again,
Charl

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/

c.p.botha ||at|| ewi.tudelft.nl - tu delft work-related email
cpbotha ||at|| cpbotha.net - everything else


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf