On Dec 11, 2006, at 04:35 , Tatsuo Ishii wrote:
That's not the whole story. UTF-8 and other variable-width encodings
don't provide a 1:1 mapping of logical characters to single bytes; in
particular, combination characters opens the possibility of multiple
different byte sequences mapping to the same code point; therefore,
string comparison in such encodings generally cannot be done at the
byte level (unless, of course, you first acertain that the strings
involved are all normalized to an unambiguous subset of your
encoding).
Can you tell me such encodings supported by PostgreSQL other
than UTF-8?
http://www.postgresql.org/docs/8.1/interactive/
multibyte.html#MULTIBYTE-CHARSET-SUPPORTED
Alexander.
