Re: jdbc pool: validationQuery vs Connection.isValid

2016-01-06 Thread Daniel Mikusa
On Wed, Jan 6, 2016 at 10:10 AM, Julian Reschke wrote: > On 2016-01-06 15:21, Christopher Schultz wrote: > >> Julian, >> >> On 1/6/16 7:42 AM, Julian Reschke wrote: >> >>> On 2016-01-06 00:06, Christopher Schultz wrote: >>> Julian, On 1/5/16 9:25 AM, Julian Reschke wrote:

Re: jdbc pool: validationQuery vs Connection.isValid

2016-01-06 Thread Julian Reschke
On 2016-01-06 15:21, Christopher Schultz wrote: Julian, On 1/6/16 7:42 AM, Julian Reschke wrote: On 2016-01-06 00:06, Christopher Schultz wrote: Julian, On 1/5/16 9:25 AM, Julian Reschke wrote: Hi there, maybe that's a stupid question, but why do we need a configurable validationQuery when

Re: jdbc pool: validationQuery vs Connection.isValid

2016-01-06 Thread Christopher Schultz
Julian, On 1/6/16 7:42 AM, Julian Reschke wrote: > On 2016-01-06 00:06, Christopher Schultz wrote: >> Julian, >> >> On 1/5/16 9:25 AM, Julian Reschke wrote: >>> Hi there, >>> >>> maybe that's a stupid question, but why do we need a configurable >>> validationQuery when there's >>> >>>Connectio

Re: jdbc pool: validationQuery vs Connection.isValid

2016-01-06 Thread Julian Reschke
On 2016-01-06 00:06, Christopher Schultz wrote: Julian, On 1/5/16 9:25 AM, Julian Reschke wrote: Hi there, maybe that's a stupid question, but why do we need a configurable validationQuery when there's Connection.isValid(...)

Re: jdbc pool: validationQuery vs Connection.isValid

2016-01-05 Thread Christopher Schultz
Julian, On 1/5/16 9:25 AM, Julian Reschke wrote: > Hi there, > > maybe that's a stupid question, but why do we need a configurable > validationQuery when there's > > Connection.isValid(...) > > Because not

jdbc pool: validationQuery vs Connection.isValid

2016-01-05 Thread Julian Reschke
Hi there, maybe that's a stupid question, but why do we need a configurable validationQuery when there's Connection.isValid(...) Best regards, Julian