Received: from netmeme.org (c1075365-a.boulder1.co.home.com [24.15.228.66])
	by hub.org (8.10.1/8.10.1) with ESMTP id e7PIPTI23891
	for <pgsql-interfaces@postgresql.org>;
	Fri, 25 Aug 2000 14:25:29 -0400 (EDT)
Received: from c1075365a ([192.168.1.2])
	by netmeme.org (8.9.3/8.9.3) with SMTP id LAA09758
	for <pgsql-interfaces@postgresql.org>; Fri, 25 Aug 2000 11:26:54 -0600
Message-ID: <08dd01c00ec1$d47183e0$0201a8c0@c1075365a>
From: "Bryan Field-Elliot" <bryan@netmeme.org>
To: <pgsql-interfaces@postgresql.org>
References: <39A577C6.52AD43D8@mhsoftware.com>
Subject: JDBC and java.sql.Timestamp
Date: Fri, 25 Aug 2000 12:25:22 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Archive-Number: 200008/158

Using the latest stable postgres and JDBC drivers, I am having a problem
which I have seen mentioned here previously; namely, that after inserting a
row with a Timestamp column, and while attempting to retrieve it again (via
JDBC), I get exceptions; I believe this is due to a bug in the format string
in the jdbc client.

Some have mentioned that a fix is available in CVS, but (believe or not) I
am newbie enough to have not yet used CVS or know how to retrieve patches
via it.

Is there a released (downloadable, even RPM-downloadable) version of the
JDBC driver with the Timestamp issue fixed?

Thanks in advance,

Bryan