RE: [Jython-users] zxJDBC not committing ?

[brian z. <bz...@zi...>]

Noel,

I have not use Poolman but have heard good things about (though I see
the SF project has stopped being supported).  I generally either use an
app server's pool if running in [Py]Servlet or a
ConnectionPooledDataSource if I'm running the interpreter or just coding
a script.  In general I don't have too many threads in scripts so it's
not generally a big deal.  When I deal with threads it's primarily in an
appserver in which case the provided pool is generally sufficient.

hope this helps,

brian

> -----Original Message-----
> From: Noel Rappin [mailto:no...@ya...] 
> Sent: Saturday, March 23, 2002 1:46 PM
> To: brian zimmer; Ale...@di...; 
> jyt...@li...
> Subject: RE: [Jython-users] zxJDBC not committing ?
> Importance: High
> 
> 
> 
> >
> >[NOTE] Since both the Python DB API and JDBC have .commit() on the 
> >connection be careful with threads.  A connection used to create 
> >cursors across threads is dangerous since one thread might call 
> >.commit() on the connection while other threads are in the middle of 
> >something.  It is best to allocate a new connection per 
> thread or use a 
> >connection pool (Datasource or otherwise) to make sure no 
> two threads 
> >are sharing a single connection.
> 
> Brian -- while we're on the subject I have a follow up 
> question... is there 
> a connection pool tool that you've used with zxJDBC that 
> works particularly 
> well (or works at all)?  I've been looking around for pool 
> tools that hit 
> the JDBC 2.0 spec (which it seems like zxJDBC needs), and 
> haven't found 
> anything that I really like.
> 
> Thanks,
> 
> Noel
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>