Received: from beast.uwillsee.com (h223124.ppp.asahi-net.or.jp [61.114.223.124]) by postgresql.org (Postfix) with ESMTP id 5746747598E for ; Mon, 4 Mar 2002 21:13:54 -0500 (EST) Received: from tom by beast.uwillsee.com with local (Exim 3.22 #1) id 16i4S9-0002LP-00; Tue, 05 Mar 2002 11:13:21 +0900 Date: Tue, 5 Mar 2002 11:13:21 +0900 From: Thomas O'Dowd To: Barry Lind Cc: Andreas Joseph Krogh , pgsql-jdbc@postgresql.org Subject: Re: [SQL] Timestamp output Message-ID: <20020305111321.H1200@beast.uwillsee.com> References: <20020226223623.L56253-100000@houston.familyhealth.com.au> <20020226175601.0944123FA1@dell-laptop01.officenet.no> <3C5FBB0C.9060304@xythos.com> <20020227222917.9BE5E3E2EE@dell-laptop01.officenet.no> <3C7EE856.9000800@xythos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C7EE856.9000800@xythos.com>; from barry@xythos.com on Thu, Feb 28, 2002 at 06:32:54PM -0800 X-Archive-Number: 200203/41 X-Sequence-Number: 3281 On Thu, Feb 28, 2002 at 06:32:54PM -0800, Barry Lind wrote: > Andreas, > > I can't reproduce the problem you are seeing. I created a table 'test' > with one column of type timestamp. Inserted one row with the value from > now(). And then ran a simple jdbc program to select out that one row. > This all worked without errors. > > Again I ask are you using the latest 7.2 driver? I know there where > some bugs in earlier 7.2 drivers (I think in all of the betas actually) > that look similar to the problem you are reporting. Yep, that should definately be fixed in the latest 7.2 driver. Also, there is a patch waiting to fix a different timestamp bug which I submitted on Thu, 17 Jan 2002 22:57:08 which fixes the usage of timestamp without the timezone. Tom. -- Thomas O'Dowd. - Nooping - http://nooper.com tom@nooper.com - Testing - http://nooper.co.jp/labs