Received: from mail.retep.org.uk ([216.126.85.184]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0UNTfq62869 for ; Tue, 30 Jan 2001 18:29:41 -0500 (EST) (envelope-from peter@retep.org.uk) Received: from heather.retep.org.uk ([193.113.119.54]) (authenticated) by mail.retep.org.uk (8.11.1/8.11.1) with ESMTP id f0UNTaO62865; Tue, 30 Jan 2001 18:29:36 -0500 (EST) (envelope-from peter@retep.org.uk) Message-Id: <5.0.2.1.0.20010130232641.00a23810@mail.retep.org.uk> X-Sender: peter@mail.retep.org.uk X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 30 Jan 2001 23:28:14 +0000 To: Joseph Shraibman From: Peter Mount Subject: Re: Re: [PATCHES] Re: [INTERFACES] Patch for JDBC timestamp problems Cc: Michael Stephenson , PostgreSQL jdbc list In-Reply-To: <3A773ED6.8B66A48B@selectacast.net> References: <3A760360.DA37F1C@selectacast.net> <980862184.3a76c4e8bf0e6@webmail.retep.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200101/102 X-Sequence-Number: 107 At 17:23 30/01/01 -0500, Joseph Shraibman wrote: >Peter T Mount wrote: > > > > Quoting Joseph Shraibman : > > > > > Michael Stephenson wrote: > > > > > > > > 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. > > > > > > But I think some people are still using java 1.1.x and they don't have > > > ThreadLocal. > > > > True, except the 1.1 & 1.2 implementations are different packages, so you > > simply don't do ThreadLocal in 1.1.x > > > >Umm, not exactly. You can use jdbc 2 with java 1.1.x by downloading a >seperate package. I'm not sure how many people do this, but I imagine >there are a few. A subset maybe, but there are some bits that reference classes introduced in JDK1.2.x and later, so would simply not work with 1.1. Peter