Re: Use CASEFOLD() internally rather than LOWER()

Поиск
Список
Период
Сортировка
Искать
От
Jeff Davis
Тема
Re: Use CASEFOLD() internally rather than LOWER()
Дата
в 22:53:42
Msg-id
9e5b70b6a45166e42b1a878e260dd2e1c76be506.camel@j-davis.com
Ответ на
Список
Дерево обсуждения
Use CASEFOLD() internally rather than LOWER() Jeff Davis <pgsql@j-davis.com>
Re: Use CASEFOLD() internally rather than LOWER() Chao Li <li.evan.chao@gmail.com>
Re: Use CASEFOLD() internally rather than LOWER() Jeff Davis <pgsql@j-davis.com>
Re: Use CASEFOLD() internally rather than LOWER() "Daniel Verite" <daniel@manitou-mail.org>
Re: Use CASEFOLD() internally rather than LOWER() Jeff Davis <pgsql@j-davis.com>
Re: Use CASEFOLD() internally rather than LOWER() Mark Dilger <mark.dilger@enterprisedb.com>
Re: Use CASEFOLD() internally rather than LOWER() Jeff Davis <pgsql@j-davis.com>
Re: Use CASEFOLD() internally rather than LOWER() Mark Dilger <mark.dilger@enterprisedb.com>
Re: Use CASEFOLD() internally rather than LOWER() Jeff Davis <pgsql@j-davis.com>
Re: Use CASEFOLD() internally rather than LOWER() Mark Dilger <mark.dilger@enterprisedb.com>
On Tue, 2026-01-13 at 10:14 +0800, Chao Li wrote:
> 1 - 0001
> ```
> +SELECT U&'straße' ILIKE U&'STRASSE' COLLATE PG_C_UTF8;
> ```
> 
> Do we want to added one more test:
> ```
> SELECT U&'straße' ILIKE U&'STRASSE' COLLATE PG_UNICODE_FAST;
>  ?column?
> ----------
>  t
> (1 row)
> ```
> Which tests the different behaviors against collations.

I am confused, doesn't the patch already have both of those tests for
both collations? What change are you suggesting?

> I initially thought to add test cases with different collations, but
> after debugging, I found that citext intentionally ignores specified
> collation.

Adding a test that's dependent on the database-wide collation is more
heavyweight because it needs to create a new database.


Regards,
	Jeff Davis



В списке pgsql-hackers по дате отправления
От: Kai Wagner
Дата:
От: Jeff Davis
Дата:
FAQ