Re: How not to use JDBC (JDBC Performance Scale 15x presentation)

I mean connection leaks, and when a connection is closed the recommended
approach is to close the ResultSets and Statements before.

Ok, I get your point, you mean to reuse the statement in a loop.

Thanks for your quick response.

Jorge Solórzano

On Wed, Mar 15, 2017 at 3:13 PM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:

> Hi Jorge,
>
> Many people do very unusual things such as create a statement for every
> iteration of the loop.
>
> I think you are correct that keeping the statement open for the life of
> the app is a bit of a stretch but ideally as long as possible.
>
> OTOH, what leaks are you referring to ? Statements end up being server
> prepared statements which should not leak.
>
> Dave Cramer
>
> davec(at)postgresintl(dot)com
> www.postgresintl.com
>
> On 15 March 2017 at 17:07, Jorge Solórzano <jorsol(at)gmail(dot)com> wrote:
>
>> Hi Dave,
>>
>> In your JDBC presentation at Scale 15x you mention that the best solution
>> to get advantage of caching is to never close the statements if possible,
>>
>> How that works? I normally (and most people I think) do a open - close
>> approach, and it's probably the best practice I think (to avoid leaks). So
>> how can a statement remain open for the lifespan of the application?
>>
>> I mostly use applications in the context of application servers, where
>> they have connection pools and their own statement cache, so is valid to
>> "enable" the statement cache of the application server and expect that the
>> driver internally use them?
>>
>
>