Re: [18] Policy on IMMUTABLE functions and Unicode updates

Поиск
Список
Период
Сортировка
От Isaac Morland
Тема Re: [18] Policy on IMMUTABLE functions and Unicode updates
Дата
Msg-id CAMsGm5eAOqM9ZebZrOXWFE-GFR-u0ngHa_j-G_hrh3t1RE8b1g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [18] Policy on IMMUTABLE functions and Unicode updates  (Jeff Davis <pgsql@j-davis.com>)
Список pgsql-hackers
Дерево обсуждения
On Mon, 22 Jul 2024 at 13:51, Jeff Davis <pgsql@j-davis.com> wrote:
 
> Are you proposing a switch that would make PostgreSQL error out if
> somebody wants to use an unassigned code point?  That would be an
> option.

You can use a CHECK(UNICODE_ASSIGNED(t)) in version 17, and in version
18 I have a proposal here to make it a database-level option:

And if you define a domain over text with this check, you would effectively have a type that works exactly like text except you can only store assigned code points in it. Then use that instead of text everywhere (easy to audit with a query over the system tables).

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jeff Davis
Дата:
Сообщение: Re: [18] Policy on IMMUTABLE functions and Unicode updates
Следующее
От: Jacob Champion
Дата:
Сообщение: Re: Add support to TLS 1.3 cipher suites and curves lists