Very cool - thanks for the link.
> -Original Message-
> From: Serge Knystautas [mailto:[EMAIL PROTECTED]
> Sent: Monday, 7 July 2003 2:31 PM
> To: Jakarta Commons Developers List
> Subject: Re: [DBCP] cpdsadapter needs a Statement implementation
>
>
> Tim An
On Sun, 2003-07-06 at 20:51, David Graham wrote:
> --- John McNally <[EMAIL PROTECTED]> wrote:
> > I recently noticed that the cpdsadapter package needs to be fixed wrt
> > the Statement.getConnection() method. It will currently return the
> > underlying physical Connection object as opposed to th
Tim Anderson wrote:
On the subject of logging, are there any plans to implement
SQL traces? I have a hacked copy of dbcp which I used
to help track down a deadlock. If there's any interest,
I'll clean it up and submit it.
I think the sense moving forward is that DBCP will remain only a pooling
imp
[EMAIL PROTECTED]
> Sent: Monday, 7 July 2003 1:51 PM
> To: Jakarta Commons Developers List
> Subject: Re: [DBCP] cpdsadapter needs a Statement implementation
>
>
> --- John McNally <[EMAIL PROTECTED]> wrote:
> > I recently noticed that the cpdsadapter package needs t
--- John McNally <[EMAIL PROTECTED]> wrote:
> I recently noticed that the cpdsadapter package needs to be fixed wrt
> the Statement.getConnection() method. It will currently return the
> underlying physical Connection object as opposed to the logical
> Connection which was used to create the State
I recently noticed that the cpdsadapter package needs to be fixed wrt
the Statement.getConnection() method. It will currently return the
underlying physical Connection object as opposed to the logical
Connection which was used to create the Statement.
When first writing cpdsapapter, I determined
