From: | Giles Lean <giles(at)nemeton(dot)com(dot)au> |
---|---|
To: | "Randall Parker" <randall(at)nls(dot)net> |
Cc: | "PostgreSQL-Dev" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: An idea on faster CHAR field indexing |
Date: | 2000-06-22 11:41:40 |
Message-ID: | 12860.961674100@nemeton.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[ I hope this is useful for the archives, even though it's pretty much
been covered already. --giles ]
> With Unicode you have to have a collation order that cuts across
> what use to be separate character sets in separate code pages.
From the glossary at http://www.unicode.org/glossary/index.html:
Collation
The process of ordering units of textual information. Collation is
usually specific to a particular language. Also known as
alphabetizing or alphabetic sorting. Unicode Technical Report #10,
"Unicode Collation Algorithm," defines a complete, unambiguous,
specified ordering for all characters in the Unicode Standard.
The "Unicode Technical Report #10" is accessible at:
http://www.unicode.org/unicode/reports/tr10/
This technical report provides a way to specify "the tailoring for any
particular country" which together with the standard ordering will
allow different Unicode implementations to sort any particular input
identically.
Summary is that Unicode still has locales and we still have to know
not only the character set/code page but also the locale ("country
specific tailoring") an index was created with to use it.
Regards,
Giles
From | Date | Subject | |
---|---|---|---|
Next Message | Giles Lean | 2000-06-22 11:58:08 | Re: Big 7.1 open items |
Previous Message | Hiroshi Inoue | 2000-06-22 11:09:07 | RE: Big 7.1 open items |