| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(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 13:13:32 |
| Message-ID: | 382ECA12-12A3-4545-9F37-0F63B0E16CD3@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Same book
JDBC API Tutorial 3rd Edition
pg 676
In fact we do this now..
On 20-Jul-05, at 8:53 AM, Oliver Jowett wrote:
> 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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2005-07-20 14:09:06 | Re: Streaming ResultSet |
| Previous Message | Oliver Jowett | 2005-07-20 12:53:24 | Re: Timestamp Conversion Woes Redux |