Dennis Bjorklund wrote:
> The named entity that is called a collation works for a character
> repertoire. It would need to handle different charsets for that
> repertoire of course. So there would be one collation called say
> ucs_sv and not utf8_sv, utf16_sv, utf32_sv.
Again, theoretically, this might work, but I doubt that this is a
practical implementation. Moreover, since Unicode is more or less the
only chararacter repertoire that have more than one encoding in use,
and neither UTF-16 nor UTF-32 can be used inside the PostgreSQL server
(embedded zero bytes etc.), this is really a nonissue.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
