"Jim Starkey" <jas@...> wrote:

>
> An exception would be character set "none", which would indicate that
> the field was raw octets and subject to no character set handling at
> all. For all practical purposes, a field of character set none is a
> different datatype with no mapping / assignment / comparison to
> character set data.

What about WIN1251 databases (in order to use non-binary collations and the
UPPER function) and NONE attachment charset (to disable any character
conversions)? I'm afraid this is even more often used than NONE databases.


Dmitry