Re: encoding affects ICU regex character classification
От
Jeff Davis
Тема
Re: encoding affects ICU regex character classification
Дата
Msg-id
3a86ea75efc0a7dd1b040d3358356c901a9c154a.camel@j-davis.com
Ответ на
Re: encoding affects ICU regex character classification (Jeremy Schneider)
Список
Дерево обсуждения
encoding affects ICU regex character classification Jeff Davis <pgsql@j-davis.com>
Re: encoding affects ICU regex character classification Tom Lane <tgl@sss.pgh.pa.us>
Re: encoding affects ICU regex character classification Jeff Davis <pgsql@j-davis.com>
Re: encoding affects ICU regex character classification Thomas Munro <thomas.munro@gmail.com>
Re: encoding affects ICU regex character classification Jeff Davis <pgsql@j-davis.com>
Re: encoding affects ICU regex character classification Thomas Munro <thomas.munro@gmail.com>
Re: encoding affects ICU regex character classification Jeff Davis <pgsql@j-davis.com>
Re: encoding affects ICU regex character classification Jeremy Schneider <schneider@ardentperf.com>
Re: encoding affects ICU regex character classification Jeff Davis <pgsql@j-davis.com>
Re: encoding affects ICU regex character classification Jeremy Schneider <schneider@ardentperf.com>
Re: encoding affects ICU regex character classification Jeff Davis <pgsql@j-davis.com>
Re: encoding affects ICU regex character classification Thomas Munro <thomas.munro@gmail.com>
On Fri, 2023-12-15 at 16:48 -0800, Jeremy Schneider wrote: > This goes back to my other thread (which sadly got very little > discussion): PosgreSQL really needs to be safe by /default/ Doesn't a built-in provider help create a safer option? The built-in provider's version of Unicode will be consistent with unicode_assigned(), which is a first step toward rejecting code points that the provider doesn't understand. And by rejecting unassigned code points, we get all kinds of Unicode compatibility guarantees that avoid the kinds of change risks that you are worried about. Regards, Jeff Davis
В списке pgsql-hackers по дате отправления