Chuck Fox wrote:

Steve,

I am a Sybase DBA, but in situations like this, I have declared the column on the table to be varbinary or binary and stored the data directly without conversion. Don't know if MySql supports this datatype.

One can declare a column "VARCHAR(n) BINARY" for a similar thing to Sybase's "VARBINARY(n)", but unfortunately it makes no difference. If I store the data directly without conversion into such a column then, as far as I can make out, each character's bytes get stored exactly as if I had converted to bytes beforehand. And when I retrieve the data (again without conversion) I just get octet sequences into my Perl scalars - not flagged, UTF-8 character strings as I would like.


This is all exactly the same as what I get with a "VARCHAR(n)" column.

- Steve

Reply via email to