Ed Dressel wrote:

>> Octets will allow 0x0 bytes, and that's what I would
>> use for encrypted data. The fact that zeros are the pad
>> character doesn't matter - most character sets use space
>> as a pad - that doesn't make space an illegal character.
>
> Thanks.
>
> What is the cost/loss of moving from NONE to Octets?

You *don\t* have to have the same character set for entire database!

I have some databases with charset WIN1250 for most of the data, and
some 'special' columns are explicitly defined as OCTETS. Nothing wrong
with that.

> Note that some databases may not have their data encrypted, others
> will. So will an un-encrypted database have the ability to sort?

For non-encrypted columns, use the most appropriate charset, for example
WIN1252 or ISO8859_1. For encrypted columns, use OCTETS.


--
Milan Babuskov
http://www.flamerobin.org