Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows
| От | Daniel Verite |
|---|---|
| Тема | Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows |
| Дата | |
| Msg-id | c00a63d3-f9c3-4222-a659-637232523b30@manitou-mail.org обсуждение исходный текст |
| Ответ на | Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows (Jehan-Guillaume de Rorthais <jgdr@dalibo.com>) |
| Ответы |
Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows
|
| Список | pgsql-bugs |
Jehan-Guillaume de Rorthais wrote: > I really have no strong feeling right now about the best solution to adopt. > However, I feel the least to do would be document it somewhere with a lot of > strong emphasis. Right now https://www.postgresql.org/docs/devel/collation.html includes this example: <quote> CREATE COLLATION digitslast (provider = icu, locale = 'en-u-kr-latn-digit'); CREATE COLLATION digitslast (provider = icu, locale = 'en@colReorder=latn-digit'); Sort digits after Latin letters. (The default is digits before letters.) </quote> Now that we know that this collation is problematic, we could remove this example, even if we don't want to go as far as documenting ICU bugs. In fact bug reports used the same name "digitslast", so I wonder if people tried this straight from our doc. Best regards, -- Daniel Vérité PostgreSQL-powered mailer: https://www.manitou-mail.org Twitter: @DanielVerite
В списке pgsql-bugs по дате отправления: