| From: | Naz Gassiep <naz(at)mira(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Data from zone.tab |
| Date: | 2008-01-08 08:35:56 |
| Message-ID: | 478335EC.9060204@mira.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Is there any reason that the zone.tab information is not included in the
pg_timezone_names system view? ISTM that there is really no reason not
to, as that view is really populated using that file anyway. There is a
1:1 mapping (assuming the aliases are mapped to the zone.tab entries
they are aliases of) of entries in that view with enties in zone.tab.
Reading an earlier thread on this matter, I think Magnus is behind the
code that generates the view. What are the chances of getting at least
the country code included in the pg_timezone_names system view? It'd
really help out with i18n / L10n work, and given that PG already ships
with that data present, it seems silly to not take advantage of it given
how easy it would be to do so.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ilanco | 2008-01-08 08:43:31 | Re: ERROR: translation failed from server encoding to wchar_t |
| Previous Message | Tomasz Ostrowski | 2008-01-08 07:06:39 | Re: Implementing Sorting Refinements |