Re: 7.3 -> 8.0.4 migration timestamp problem - Mailing list pgsql-jdbc

From Eliézer Madeira de Campos
Subject Re: 7.3 -> 8.0.4 migration timestamp problem
Date
Msg-id 54CC7CADE26E884EB2BCEC863F5C1F70F9D282@moscou.diuno.net
Whole thread Raw
In response to 7.3 -> 8.0.4 migration timestamp problem  (Eliézer Madeira de Campos <eliezer@diuno.com.br>)
List pgsql-jdbc


-----Original Message-----
From: Oliver Jowett [mailto:oliver@opencloud.com]
Sent: sexta-feira, 4 de novembro de 2005 20:20
To: Eliézer Madeira de Campos
Cc: pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] 7.3 -> 8.0.4 migration timestamp problem

Eliézer Madeira de Campos wrote:

>>     The date stored in database is actually 1912-12-31 23:53:12.0 (however it should have stored 1913-01-01.
>>
>>     I have already debugged the Postgres-8.0 (build 313) driver and it seems to send the correct date to database.

> What type is the target column you are inserting into?
Timestamp without timezone.

>>       Timestamp ts = new Timestamp(c.getTimeInMillis());
>>       pst = con.prepareStatement("select date_trunc('day', TIMESTAMP ?)");
>>       pst.setObject(1, ts);

> Use "CAST (? AS TIMESTAMP)" instead of "TIMESTAMP ?".
Why should I, if "TIMESTAMP ?" works when I run the insert in psql (or via unprepared statement)?
That might be valid as a workaround, but it would cost me thousands changes in the application, so it's not really a
solutionto the problem. 

Eliézer M de Campos

pgsql-jdbc by date:

Previous
From: Eliézer Madeira de Campos
Date:
Subject: 7.3 -> 8.0.4 migration timestamp problem
Next
From: Oliver Jowett
Date:
Subject: Re: 7.3 -> 8.0.4 migration timestamp problem