| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Thomas Lockhart <lockhart(at)fourpalms(dot)org>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More time zones |
| Date: | 2002-02-26 03:22:55 |
| Message-ID: | 26770.1014693775@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> One concern I have about the time zone abbreviation database is that the
> inflation of possible choices makes any kind of error checking mostly
> non-existant.
That's overstated, but it's a good point nonetheless. We had a report
of one missing timezone entry (or was it two?). Not sure that that
should prompt us to add a hundred entries of dubious validity to the
keyword list.
Perhaps we could find some middle ground between a hard-wired list and
looking up TZ entries in a fully dynamic system table. The list of
known timezones seems like something we could read from a flat text
configuration file at startup --- wouldn't that be enough
configurability?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2002-02-26 03:38:52 | Re: More time zones |
| Previous Message | Arguile | 2002-02-26 03:11:02 | Timezone Inconsistancies |