| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Arthur Zakirov <zaartur(at)gmail(dot)com>, Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Allow to_date() and to_timestamp() to accept localized names |
| Date: | 2020-01-23 16:49:55 |
| Message-ID: | 20200123164955.GA23074@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Jan-23, Tom Lane wrote:
> That particular case could be improved by stopping at a dash ... but
> since this code is also used to match strings like "A.M.", we can't
> just exclude punctuation in general. Breaking at whitespace seems
> like a reasonable compromise.
Yeah, and there are cases where dashes are used in names -- browsing
through glibc for example I quickly found Akan, for which the month names are:
mon "Sanda-<U0186>p<U025B>p<U0254>n";/
"Kwakwar-<U0186>gyefuo";/
"Eb<U0254>w-<U0186>benem";/
and so on. Even whitespace is problematic for some languages, such as Afan,
mon "Qunxa Garablu";/
"Naharsi Kudo";/
"Ciggilta Kudo";/
(etc) but I think whitespace-splitting is going to be more comprehensible
in the vast majority of cases, even if not perfect.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jehan-Guillaume de Rorthais | 2020-01-23 16:54:08 | Re: Fetching timeline during recovery |
| Previous Message | Pavel Stehule | 2020-01-23 16:39:01 | Re: New feature proposal (trigger) |