Dave Cramer wrote:
> Actually,
>
> Java has timezones that postgres doesn't understand, which is
> why using the server timezone makes more sense.
>
> Hopefully java understands all the timezones postgres understands.
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)
