Re: help with front/backend datatype converting

From: "Do, Leon \(Leon\)" <leondo(at)lucent(dot)com>
To: "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: 2006-11-15 04:36:30
Message-ID: D1EE06BA46B1E4449AF9A4F2FBEE18612BE651@ILEXC2U01.ndc.lucent.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

> -----Original Message-----
> From: Oliver Jowett [mailto:oliver(at)opencloud(dot)com]
> Sent: Tuesday, November 14, 2006 6:06 PM
> To: Do, Leon (Leon)
> Cc: Dave Cramer; imad; pgsql-jdbc(at)postgresql(dot)org
> Subject: Re: [JDBC] help with front/backend datatype converting
>
> Do, Leon (Leon) wrote:
>
> > I think postgres has a few bugs in this area. When timezone
doesn't
> > have a semicolon between hour and min, TimestampUtil.java cann't
handle
> > it. The firstNonDigits method call below returns all four digits
and
> > assigns them to timezone hour variable.
>
> Does the server ever generate timezones like this?
I haven't tested the server side but I know the client generates that
format but it didn't take what it generated.
>
> > And for the second bugs, fractional part of the second (e.g.
> > 14:36:19.213000) seem to be interpreted incorrectly when converting
to
> > Java Date. 213000 would round up as additional 3.52 mins.

>
> Testcase please?
Sorry, this was my mistake when using java SimpleDateFormatter class and
assumed the second fractional part as millisecond instead of nanosecond.

thanks
Leon Do
>
> -O

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Håkan Jacobsson 2006-11-15 08:32:42 Re: Need help with org.postgresql.util.PSQLException: An I/O error occured while
Previous Message Reuben Pasquini 2006-11-15 04:05:22 CallableStatement.setTimestamp bug