| 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 01:58:16 |
| Message-ID: | 15EA293E-6D5D-4FD2-B498-6546113822C1@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Christian suggested this:
However I think this too opaque.
Not to mention the fact that it changes the
current behaviour.
Dave
On 19-Jul-05, at 9:41 PM, Oliver Jowett wrote:
> Christian Cryder wrote:
>
>
>> From my perspective, there needs to be a way for the JDBC driver to
>> know what type of timestamp you are working with. [...]
>>
>
> How about this mapping?
>
> setTimestamp(int,Timestamp) -> timestamp
> setTimestamp(int,Timestamp,Calendar) -> timestamptz
>
> -O
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-07-20 01:59:21 | Re: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block |
| Previous Message | Oliver Jowett | 2005-07-20 01:41:02 | Re: Timestamp Conversion Woes Redux |