> > The Database.
> >
> > - All entries should be stored as Unicode. Or to be more correct, the
> > database should input and output unicode data, how it is stored is of no
> > concern to me. If we are to get an IETF approval of any protocols they
> > have to support unicode according to their new guidelines.
>
> Ah. Actually, my current database design
> (http://www.cdin.org/impl/tables.html) has the columns as "VARCHAR". I
> need to look at the MySQL doc to see if that is 8-bit compatible. It
> probably is (and BINARY just means that \0 can be stored).
MySQL is 8-bit compatible and you can store all 256 characters in
VARCHAR (you only have to quote ' and \0 AFAIK without reading the
doku). BINARY is not relevant on this part of the issue.
BINARY means, that the VARCHAR field will be regarded case sensitive
regarding comparisons (i.e. sorting and indexes). So you have to use
VARCHAR BINARY to be able to handle unicode (also UTF8) properly.
Bye,
Benjamin.