Re: ICU locale validation / canonicalization

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: ICU locale validation / canonicalization
Дата
Msg-id 857da8b1-2a1e-a2be-7df9-7f5e85a3bcb7@enterprisedb.com
обсуждение исходный текст
Ответ на Re: ICU locale validation / canonicalization  (Jeff Davis <pgsql@j-davis.com>)
Ответы Re: ICU locale validation / canonicalization  (Jeff Davis <pgsql@j-davis.com>)
Список pgsql-hackers
On 09.03.23 21:17, Jeff Davis wrote:
>> Personally, I'm not on board with this behavior:
>>
>> => CREATE COLLATION test (provider = icu, locale =
>> 'de@collation=phonebook');
>> NOTICE:  00000: using language tag "de-u-co-phonebk" for locale
>> "de@collation=phonebook"
>>
>> I mean, maybe that is a thing we want to do somehow sometime, to
>> migrate
>> people to the "new" spellings, but the old ones aren't wrong.
> 
> I see what you mean; I'm not sure the best thing to do here. We are
> adjusting the string passed by the user, and it feels like some users
> might want to know that. It's a NOTICE, not a WARNING, so it's not
> meant to imply that it's wrong.

For clarification, I wasn't complaining about the notice, but about the 
automatic conversion from old-style ICU locale ID to language tag.

>> It also doesn't appear to address
>> how to handle ICU before version 54.
> 
> Do you have a specific concern here?

What we had discussed a while ago in one of these threads is that ICU 
before version 54 do not support keyword lists, and we have custom code 
to do that parsing ourselves, but we don't have code to do the same for 
language tags.  Therefore, if I understand this right, if we 
automatically convert ICU locale IDs to language tags, as shown above, 
then we break support for such locales in those older ICU versions.



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

Предыдущее
От: vignesh C
Дата:
Сообщение: Re: Add macros for ReorderBufferTXN toptxn
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] Align GSS and TLS error handling in PQconnectPoll()