Dmitry Yemanov wrote:

>"Jim Starkey" <jas@...> wrote:
>
>
>>Could you describe the problems you expect?
>>
>>
>
>1) Any long index of charset WIN1251 (binary collation) may become
>unrestorable as the key will be twice longer.
>
>

Why would be key be twice as long? A collation is, in essense, a
mapping to a byte sequence that compares naturally. That collation
would map unicode characters back into the WIN1251 character. Unless
somebody has done something silly, the keys should be the same.

>2) How are you going to maintain compatibility of charset NONE attachments?
>
>

I anticipate that the API proper will pass only UTF-8 strings but there
will be client-side layered calls to map to and from specific or
platform default character sets. I will confess, however, that I
haven't a clue of what charset NONE is supposed to mean. I don't
suppose that it means that data types are limited to numbers...

--

Jim Starkey
Netfrastructure, Inc.
978 526-1376