| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Franois LECOMTE <francois(dot)lecomte(at)oosphere(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1525: wrong time when getting timestamp from date |
| Date: | 2005-03-05 05:11:06 |
| Message-ID: | Pine.BSO.4.56.0503050007080.32493@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, 4 Mar 2005, Franois LECOMTE wrote:
> Bug reference: 1525
> PostgreSQL version: 8.0.1
> Description: wrong time when getting timestamp from date field
>
> Problem when getting a Java Timestamp object on a DATE database field.
> With driver pg74jdbc3.jar : hours, minutes, seconds and millis have zero
> values (ex : "2003-09-10 00:00:00.0") in the Timestamp object, no problem.
> With driver postgresql-8.0-310.jdbc3.jar (same database, same table, same
> record) : we get 1 hour and zero minutes, seconds and millis ! ("2003-09-10
> 01:00:00.0")
> Maybe UTC time ? but suerly a bug...
>
There is a known bug in the 8.0 jdbc driver when the client and server are
in different timezones. Is that the case here?
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-03-05 06:20:27 | Re: BUG #1527: select retrieves 0 rows after vacuum analyze |
| Previous Message | Tom Lane | 2005-03-05 04:49:20 | Re: BUG #1526: SHRT_MIN out of range on explicit type conversion |