RE: BUG #15651: Collation setting en_US.utf8 breaking sort order
От | Kaleb Akalework |
---|---|
Тема | RE: BUG #15651: Collation setting en_US.utf8 breaking sort order |
Дата | |
Msg-id | 9421be5798da48c0a265bc13b0ef5224@asg.com обсуждение исходный текст |
Ответ на | Re: BUG #15651: Collation setting en_US.utf8 breaking sort order (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: BUG #15651: Collation setting en_US.utf8 breaking sort order
RE: BUG #15651: Collation setting en_US.utf8 breaking sort order |
Список | pgsql-bugs |
Ok so if this is intended behavior of UTF8 then I understand. My last question then would be if I use a collation settingof C, does it mean I won't be able to support multiple languages? -----Original Message----- From: Peter Geoghegan <pg@bowt.ie> Sent: Friday, February 22, 2019 1:41 PM To: Tom Lane <tgl@sss.pgh.pa.us> Cc: Kaleb Akalework <kaleb.akalework@asg.com>; PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org> Subject: Re: BUG #15651: Collation setting en_US.utf8 breaking sort order *** External email: Verify sender before opening attachments or links *** On Fri, Feb 22, 2019 at 10:03 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > This appears to be the intended behavior of en_US sorting. Right. UCA style algorithms tend to give the least weight of all to whitespace characters. They're tertiary weight, if memoryserves. -- Peter Geoghegan
В списке pgsql-bugs по дате отправления: