Re: Timestamp Conversion Woes Redux

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Timestamp Conversion Woes Redux
Date: 2005-07-20 12:53:24
Message-ID: 42DE4944.3010302@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dave Cramer wrote:
> Yes, it does, my mistake ( It was early here )
>
> However reading the notes about setTimestamp:
>
> When the DBMS does not store timezone information the driver will use
> cal to construct a JDBC Timestamp value.
> If no Calendar object is specified the driver uses the timezone of the
> JVM.

Where's this from exactly? It doesn't seem to make sense if it's talking
about setTimestamp -- the driver does not construct a JDBC timestamp in
setTimestamp at all, it's given one by the application.

-O

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2005-07-20 13:13:32 Re: Timestamp Conversion Woes Redux
Previous Message Dave Cramer 2005-07-20 12:47:47 Re: Timestamp Conversion Woes Redux