Re: Latest on CITEXT 2.0
От | David E. Wheeler |
---|---|
Тема | Re: Latest on CITEXT 2.0 |
Дата | |
Msg-id | 7998C08A-D40B-4081-A343-1EA1B3FA7976@kineticode.com обсуждение исходный текст |
Ответ на | Re: Latest on CITEXT 2.0 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Latest on CITEXT 2.0
|
Список | pgsql-hackers |
On Jun 26, 2008, at 10:02, Tom Lane wrote: > BTW, I don't think you can use that same-length optimization for > citext. There's no reason to think that upper/lowercase pairs will > have the same length all the time in multibyte encodings. I was wondering about that. I had been thinking of canonically- equivalent stings and combining marks. Doing a quick test it looks like combining marks are not equivalent. For example, this returns false: SELECT 'Ä'::text = 'Ä'::text; At least with en_US.UTF-8. Hrm. It looks like my client makes them both canonical, so I've attached a script demonstrating this issue. Anyway, I was aware of different byte counts for canonical equivalence, but not for differences between upper- and lowercase characters. I'd certainly defer to your knowledge of how these things truly work in PostgreSQL, Tom, and can of course easily remove that optimization. So, are your certain about this? Many thanks, David
Вложения
В списке pgsql-hackers по дате отправления: