From: | Jim Caley <caley(at)chesco(dot)com> |
---|---|
To: | John Thorhauer <jthorhauer(at)phoenixcolor(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: java.sql.SQLException: Bad Timestamp Format at 19 in 2000-06-14 15:48:18.80-04 |
Date: | 2000-06-16 13:03:21 |
Message-ID: | 394A2599.76380445@chesco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hi John,
We've been discussing this very issue on this mailing list over the past
couple of days. If you go to
http://www.postgresql.org/mhonarc/pgsql-interfaces/2000-06/threads.html
and search the page for "Timestamps" you'll see the thread (actually, I
just checked, and at the moment the thread is right at the top of the
page). The first message in the thread includes a patch that's been
working for me.
HTH
Regards,
Jim
--
John Thorhauer wrote:
>
> I am using postgres 7.0 and and jdbc driver ver 7.0 on linux and am
> getting the following error:
>
> Exception: java.sql.SQLException: Bad Timestamp Format at 19 in
> 2000-06-14 15:48:18.80-04
>
> If I edit my the timestamp field in my table and change the data from
> '2000-06-14 10:04:47.13-04' to '2000-06-14 10:04:47' everything seems
> to work fine.
>
> I tried using the 6.5-1.2 jdbc and got the same result.
> Can anyone help me with this?
>
> Thanks,
> John Thorhauer
> --
> ********************************
> ** John Thorhauer
> ** Web Developer
> ** Phoenix Color Corp.
> ** jthorhauer(at)phoenixcolor(dot)com
> ********************************
From | Date | Subject | |
---|---|---|---|
Next Message | Nissim | 2000-06-16 14:43:19 | [PATCH] Datatype of OID should be VARBINARY, not INT |
Previous Message | Agnieszka Lesinska | 2000-06-16 10:34:49 | HELP:[pq++]:constructor `PgDatabase::PgDatabase()' is protected |