Re: JDBC and java.sql.Timestamp - Mailing list pgsql-interfaces

From Peter Mount
Subject Re: JDBC and java.sql.Timestamp
Date
Msg-id 00a301c00f46$a8a84020$2516989e@heather
Whole thread Raw
In response to JDBC Patch  (Christopher Cain <ccain@mhsoftware.com>)
List pgsql-interfaces
Also, because I've been busy the last few months, I've not done anything
since 7.0 was released. I'm spending Monday catching up with the major
outstanding stuff with JDBC, and will get a compiled copy online.

Peter

--
Peter T Mount  peter@retep.org.uk, me@petermount.com
Homepage: http://www.retep.org.uk Contact details: http://petermount.com
PostgreSQL JDBC: http://www.retep.org.uk/postgres/
Java PDF Generator: http://www.retep.org.uk/pdf/
----- Original Message -----
From: "Joseph Shraibman" <jks@selectacast.net>
To: <pgsql-interfaces@postgresql.org>
Sent: Friday, August 25, 2000 8:29 PM
Subject: Re: [INTERFACES] JDBC and java.sql.Timestamp


> I'm thinking it would justify a 7.0.3 release of postgres just to keep
> the traffic about the Timestamp off the mailing list.
>
> Bryan Field-Elliot wrote:
> >
> > 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?
> >
> The official jdbc homepage is http://www.retep.org.uk/postgres/ but it
> appears to be the 7.0 driver. Peter?
>
>
> > Thanks in advance,
> >
> > Bryan



pgsql-interfaces by date:

Previous
From: "Peter Mount"
Date:
Subject: Re: JDBC and java.sql.Timestamp
Next
From: "Peter Mount"
Date:
Subject: Re: JDBC + large objects problem