Re: [PATCHES] Re: [INTERFACES] Patch for JDBC timestamp problems - Mailing list pgsql-jdbc

From Michael Stephenson
Subject Re: [PATCHES] Re: [INTERFACES] Patch for JDBC timestamp problems
Date
Msg-id Pine.LNX.4.30.0101250949190.20707-100000@tirin.openworld.co.uk
Whole thread Raw
In response to Re: [PATCHES] Re: [INTERFACES] Patch for JDBC timestamp problems  (Joseph Shraibman <jks@selectacast.net>)
List pgsql-jdbc
On Wed, 24 Jan 2001, Joseph Shraibman wrote:

> > What was the conclusion of this discussion?  Do we leave it static?
>
> No, it cannot be static.

As I see it we have three possible solutions to this problems.

a) Just stop it being static, each PreparedStatement gets a new
   instantiation (I think this is what we've done for now).
b) static ThreadLocal, each Thread gets one instantiation.
c) An Object Pool (possibly using SoftReferences to stop memory bloat),
   slightly more difficult to code, a lot less instantiations, much
   better performance.

If people agree that either 'b' or 'c' is a better solution, I'll go ahead
and implement it.

Michael Stephenson      mstephenson@openworld.co.uk
Developer   -    Web Applications    -   Open World
Tel: +44 1225 444 950         Fax: +44 1225 336 738


pgsql-jdbc by date:

Previous
From: Peter T Mount
Date:
Subject: Re: [GENERAL] jdbc driver, error trapping.
Next
From: "Ramachandra K.B.S"
Date:
Subject: RE: Re: Postgresql JDBC driver - Support for Scrollable Re sult Sets