Re: help with front/backend datatype converting - Mailing list pgsql-jdbc

From Do, Leon \(Leon\)
Subject Re: help with front/backend datatype converting
Date
Msg-id D1EE06BA46B1E4449AF9A4F2FBEE18615E3474@ILEXC2U01.ndc.lucent.com
Whole thread Raw
In response to Re: help with front/backend datatype converting  (Kris Jurka <books@ejurka.com>)
Responses Re: help with front/backend datatype converting
List pgsql-jdbc
It would be nice if you can add a support for parsing hh:mm as well as
hhmm to conform to ISO8601.  There are many other uses of this class.  I
sent the changes earlier.

Thanks

Leon Do

> -----Original Message-----
> From: Kris Jurka [mailto:books@ejurka.com]
> Sent: Thursday, January 04, 2007 7:35 PM
> To: Oliver Jowett
> Cc: Do, Leon (Leon); Dave Cramer; imad; pgsql-jdbc@postgresql.org
> Subject: Re: [JDBC] help with front/backend datatype converting
>
>
>
> On Fri, 17 Nov 2006, Oliver Jowett wrote:
>
> > Do, Leon (Leon) wrote:
> >
> >> I haven't tested the server side but I know the client
> generates that
> >> format but it didn't take what it generated.
> >
> > Well, in general we only care about parsing what the server
> generates,
> > not what the driver generates.
> >
> > One exception might be updateable resultsets.
> >
> > The solution is probably to fix the generation side so we
> generate the
> > same format as the server produces.
> >
>
> I have fixed this in CVS for 8.0, 8.1, 8.2, and 8.3dev.
>
> Kris Jurka
>

pgsql-jdbc by date:

Previous
From: "Do, Leon \(Leon\)"
Date:
Subject: Re: need to update TimestampUtils code
Next
From: Ravi Periasamy
Date:
Subject: Re: issues with Statement.getTimestamp(int, Calendar)