| 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 02:02:24 |
| Message-ID: | 42DDB0B0.1020006@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Dave Cramer wrote:
> Christian suggested this:
>
> However I think this too opaque.
Why do you think this? There's no timezone information associated with a
Timestamp, so it seems like the logical mapping: if you provide a
timezone via Calendar, it's a timestamp-with-timezone; otherwise, it's a
timestamp-without-timezone.
> Not to mention the fact that it changes the
> current behaviour.
Err, given that the current behaviour is broken, is this a problem?
Every time I've looked at the timestamp code I've gone "ow, that has to
be broken" but never got around to investigating further .. IMO, this is
an area that the driver just gets *wrong* and we should be fixing it so
it works, not trying to support applications that expect the wrong
behaviour!
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-07-20 02:27:17 | Re: Timestamp Conversion Woes Redux |
| Previous 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 |