Re: Add CASEFOLD() function.
От | Thom Brown |
---|---|
Тема | Re: Add CASEFOLD() function. |
Дата | |
Msg-id | CAA-aLv57dEeoX__Osx4k2yda6G2V-i=MYxr0HrH6U+yyYw5wKQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Add CASEFOLD() function. (Peter Eisentraut <peter@eisentraut.org>) |
Список | pgsql-hackers |
On Thu, 19 Jun 2025 at 15:51, Peter Eisentraut <peter@eisentraut.org> wrote: > > On 19.06.25 06:03, Thom Brown wrote: > > Late to the party, but is there an argument for porting this to the > > citext type? Or supplementing the extension with an additional type > > ("cftext"? *shrug*). It currently uses lower(), so our current > > recommendation for dealing with all unicode characters is to use > > nondeterministic collations. > > What is the motivation for wanting a citext variant instead of using > nondeterministic collations? Ease of use, perhaps. It seems easier to use: column_name cftext rather than: CREATE COLLATION case_insensitive_collation ( PROVIDER = icu, LOCALE = 'und-u-ks-level2', DETERMINISTIC = FALSE ); column_name text COLLATE case_insensitive_collation But I see the arguments against it. It creates an unnecessary dependency on an extension, and if someone wants to ignore both case and accents, they may resort to using 2 extensions (citext + unaccent) when none are needed. I guess I don't feel strongly about it either way. Thom
В списке pgsql-hackers по дате отправления: