| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Oliver Siegmar <o(dot)siegmar(at)vitrado(dot)de> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Problems with infinity |
| Date: | 2005-02-04 09:27:21 |
| Message-ID: | Pine.BSO.4.56.0502040418140.17928@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 4 Feb 2005, Oliver Siegmar wrote:
> To track down the problem (infinity in another timezone) I changed the
> timezone of my PgSQL server from 'CET' to 'EST'. Even without the
> infinity-patch applied I get a test-exception:
>
> testGetTimestampWTZ(org.postgresql.test.jdbc2.TimestampTest): FAILED
> [junit] expected:<-627872399900> but was:<-627847199900>
This is a known problem when you have timestamp without time zone and the
server and client timezone is different. If you set your client timezone
to EST as well it should go away.
http://archives.postgresql.org/pgsql-jdbc/2004-12/msg00137.php
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-02-04 09:54:16 | Re: BUG #1459: Connection hangs when other connection is not committed |
| Previous Message | Oliver Siegmar | 2005-02-04 09:12:03 | Re: Problems with infinity |