| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | Dave Cramer <davec(at)fastcrypt(dot)com>, Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Timestamp Conversion Woes Redux |
| Date: | 2005-07-20 19:50:38 |
| Message-ID: | Pine.BSO.4.56.0507201450060.19284@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, 20 Jul 2005, John R Pierce wrote:
> as we discovered the hard way, named timezones are a BAD IDEA. We had some
> stuff in java + jdbc + postgres that used a timezone, when it was brought up in
> Singapore, their local timezone memnonic wasn't recognized by postgres, and
> when it was brought up in China, CST was misinterpretted as Central Standard
> Time rather than China Standard Time (about 12 hours off)
>
No, this indicates that *abbreviated* timezones are a bad idea, not named
timezones.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-07-20 20:14:09 | Re: Timestamp Conversion Woes Redux |
| Previous Message | Dave Cramer | 2005-07-20 19:42:45 | Re: Java's set of timezone names |