Re: support for DIN SPEC 91379 encoding

Поиск
Список
Период
Сортировка
От Bzm@g
Тема Re: support for DIN SPEC 91379 encoding
Дата
Msg-id 8C7FD2B2-D81E-4CED-A5B9-F9CB29605160@2bz.de
обсуждение исходный текст
Ответ на Re: support for DIN SPEC 91379 encoding  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-general
U+0000 is not part of DIN SPEC 91379.

--
Boris


> Am 27.03.2022 um 19:47 schrieb Alvaro Herrera <alvherre@alvh.no-ip.org>:
>
> On 2022-Mar-27, Ralf Schuchardt wrote:
>
>> where did you read, that this DIN SPEC 91379 norm is incompatible with UTF-8?
>>
>> In the document „String.Latin+ 1.2: eine kommentierte und erweiterte
>> Fassung der DIN SPEC 91379. Inklusive einer umfangreichen Liste häufig
>> gestellter Fragen. Herausgegeben von der Fachgruppe String.Latin“
>> linked here https://www.xoev.de/downloads-2316#StringLatin it is said,
>> that the spec is a strict subset of unicode (E.1.6), and it is also
>> mentioned in E.1.4, that in UTF-8 all unicode characters can be
>> encoded. Therefore UTF-8 can be used to encode all DIN SPEC 91379
>> characters.
>
> So the remaining question is whether DIN SPEC 91379 requires an
> implementation to support character U+0000.  If it does, then PostgreSQL
> is not conformant, because that character is the only one in Unicode
> that we don't support.  If U+0000 is not required, then PostgreSQL is
> okay.
>
> --
> Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
>
>




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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: support for DIN SPEC 91379 encoding
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: Performance issues on FK Triggers after replacing a primary column