Re: [PATCHES] Australian timezone configure option - Mailing list pgsql-hackers

From chris.bitmead@health.gov.au
Subject Re: [PATCHES] Australian timezone configure option
Date
Msg-id CA256A6B.00081157.00@mtascbr01.notes.health.gov.au
Whole thread Raw
Responses Re: Re: [PATCHES] Australian timezone configure option  (ncm@zembu.com (Nathan Myers))
List pgsql-hackers


>I will point out that "you Australians", and, well, "us 'mericans", are
>the only countries without the sense to choose unique conventions for
>time zone names.

I once had a long discussion about that on the timezone mailing lists.
If I remember right I think the upshot is that these are not the only
conflicts, they're probably just the only conflicts you have run across.

>It sounds like having a second lookup table for the Australian rules is
>a possibility, and this sounds fairly reasonable to me. Btw, is there an
>Australian convention for referring to North American time zones for
>those zones with naming conflicts?

Well aren't there long names for all the zones like Australia/NSW,
Australia/QLD, Australia/VIC etc?
I have at times heard people refer to AEST meaning Australian Eastern standard
time. I agree it's a big
mess but I couldn't even convince the timezone people there was even a problem.
Oh well.





pgsql-hackers by date:

Previous
From: "s"
Date:
Subject: how to get number of rows affected by the sql last statement?
Next
From: Tom Lane
Date:
Subject: Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards