to look into this.
>>
>> Can you think of a better propertyname than
>> limitPreparedStatementPoolToConnectionUse? While the meaning is clear (at
>> least to me), it's also quite long.
>>
>> Robert
>>
>>
>> From: Phil Steitz
>> Sent: Dienstag, 30. Juni 2020
so quite long.
>
> Robert
>
>
> From: Phil Steitz
> Sent: Dienstag, 30. Juni 2020 21:07
> To: dev@commons.apache.org
> Subject: Re: [DBCP] poolPreparedStatements
>
>
> On 6/29/20 12:17 PM, Robert Paschek wrote:
> > Hello,
> >
> > DBCP
to
use.
Robert
From: Gary Gregory
Sent: Montag, 29. Juni 2020 23:37
To: Commons Developers List
Subject: Re: [DBCP] poolPreparedStatements
You can do this today by using two connection pools, one configured with
statement pooling, and the other not (which is the default).
Gary
On Mon, Jun 29
@commons.apache.org
Subject: Re: [DBCP] poolPreparedStatements
On 6/29/20 12:17 PM, Robert Paschek wrote:
> Hello,
>
> DBCP has a feature to pool PreparedStatements for the lifetime of a
> connection.
> This results in cursors being open and locks in the database for a long
On 6/29/20 12:17 PM, Robert Paschek wrote:
Hello,
DBCP has a feature to pool PreparedStatements for the lifetime of a connection.
This results in cursors being open and locks in the database for a long time,
which could cause problems with administrative tasks in the database. That why
I
You can do this today by using two connection pools, one configured with
statement pooling, and the other not (which is the default).
Gary
On Mon, Jun 29, 2020, 16:36 Robert Paschek
wrote:
> Hello,
>
> DBCP has a feature to pool PreparedStatements for the lifetime of a
> connection.
> This
Hello,
DBCP has a feature to pool PreparedStatements for the lifetime of a connection.
This results in cursors being open and locks in the database for a long time,
which could cause problems with administrative tasks in the database. That why
I would prefer this pool to be more short-living,
