From: | "Do, Leon \(Leon\)" <leondo(at)alcatel-lucent(dot)com> |
---|---|
To: | "Kris Jurka" <books(at)ejurka(dot)com>, "Oliver Jowett" <oliver(at)opencloud(dot)com> |
Cc: | "Dave Cramer" <pg(at)fastcrypt(dot)com>, "imad" <immaad(at)gmail(dot)com>, <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: help with front/backend datatype converting |
Date: | 2007-01-05 15:53:53 |
Message-ID: | D1EE06BA46B1E4449AF9A4F2FBEE18615E3474@ILEXC2U01.ndc.lucent.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)ejurka(dot)com]
> Sent: Thursday, January 04, 2007 7:35 PM
> To: Oliver Jowett
> Cc: Do, Leon (Leon); Dave Cramer; imad; pgsql-jdbc(at)postgresql(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2007-01-05 17:17:55 | Re: help with front/backend datatype converting |
Previous Message | Do, Leon (Leon) | 2007-01-05 15:47:28 | Re: need to update TimestampUtils code |