Could this be a *client* issue rather than a *server* issue?
If the client table is encoded in a 1-byte-per-character charset,
but the client (session) tells the server that he wants that data in UTF-8,
some characters (accent letters, currency sign, ...) would be returned as 2 or
3 bytes. I.e., with a maximum of 3 bytes per character.
Which would effectively give you 105 bytes for the "description" column when
its value is all euro signs, for example.
In in "standard" command-line client this session choice would be set in
my.ini under the name default-character-set, if I'm not mistaken.
Changing its value from utf8 to latin1 could maybe "solve" the problem.
-- Peter Vanroose
Leuven, Belgium.
