Re: Allow to_date() and to_timestamp() to accept localized month names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mattia <mattia(at)p2pforum(dot)it>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow to_date() and to_timestamp() to accept localized month names
Date: 2016-09-10 15:41:18
Message-ID: 19809.1473522078@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mattia <mattia(at)p2pforum(dot)it> writes:
> attached is a patch which adds support to localized month names in
> to_date() and to_timestamp() functions.

Seems like a fine goal.

> I thought about reusing from_char_seq_search() but localized month
> names use different capitalization according to the language grammar,
> so I used pg_strncasecmp to do the match.

pg_str(n)casecmp is really only meant to handle comparisons of ASCII
strings; it will definitely not succeed in case-folding multibyte
characters. That's not a big problem for to_date's existing usages
but I'm afraid it will be for non-English month names. I think you'll
need another solution there. You might have to resort to what citext
does, namely apply the full lower() transformation, at least whenever
the data string actually contains MB characters.

> Regression tests with TM modifier are difficult since one should have
> the locale used for the test installed on his system.

I suspect you'll have to give up on putting much about this into the
standard regression tests. We've used not-run-by-default test scripts
in some similar cases (eg collate.linux.utf8.sql), but personally I think
those are 99% a waste of time, precisely because they never actually
get run by anyone but the author.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Adam Brightwell 2016-09-10 15:49:01 Re: COPY command with RLS bug
Previous Message Robert Haas 2016-09-10 15:03:14 Re: WAL consistency check facility