Re^2: OT? Character set issues with MySQL/CGI::Application

When I inserted the Español into the DB, I used a manual query in the mysql shell and copied and pasted it from a web page.

I've been trying to "fix" hte table tonight by playing around with the character set, but

ALTER TABLE Language CONVERT TO latin1;

has no effect on the data. I still have to pipe it through Encode::decode.

Comment on Re^2: OT? Character set issues with MySQL/CGI::Application Download Code

Replies are listed 'Best First'.
Re^3: OT? Character set issues with MySQL/CGI::Application by Corion (Patriarch) on Jul 25, 2008 at 06:49 UTC
How do you know what encoding the mysql shell uses? How do you know what your console uses as encoding? How do you know what the web browser did with the encoded data before putting it into the clipboard? You need to eliminate as many conversion steps as possible and check the consistency of the remaining. I wouldn't rely on MySQL to upgrade or change the encoding. Use ~~Scalar::Util~~Devel::Peek to dump the scalars before sending them to the DB to see whether Perl encodes them as UTF8 or Latin1. Then retrieve them via DBI and check the encoding again. It should be the same as you put in, but maybe it isn't. Also, the strings should ideally be bytewise identical. If Encode::decode() works, then likely your data is in UTF8 when you retrieve it from MySQL. If it already is in UTF8 when you put it in, it could be an idea to keep all data in UTF8 throughout your application and just convert at the output stage to Latin1. Update: moritz pointed out that I want Devel::Peek, not Scalar::Util	[reply]

Replies are listed 'Best First'.

Re^3: OT? Character set issues with MySQL/CGI::Application
by Corion (Patriarch) on Jul 25, 2008 at 06:49 UTC

How do you know what encoding the mysql shell uses? How do you know what your console uses as encoding? How do you know what the web browser did with the encoded data before putting it into the clipboard?

You need to eliminate as many conversion steps as possible and check the consistency of the remaining. I wouldn't rely on MySQL to upgrade or change the encoding. Use ~~Scalar::Util~~Devel::Peek to dump the scalars before sending them to the DB to see whether Perl encodes them as UTF8 or Latin1. Then retrieve them via DBI and check the encoding again. It should be the same as you put in, but maybe it isn't. Also, the strings should ideally be bytewise identical.

If Encode::decode() works, then likely your data is in UTF8 when you retrieve it from MySQL. If it already is in UTF8 when you put it in, it could be an idea to keep all data in UTF8 throughout your application and just convert at the output stage to Latin1.

Update: moritz pointed out that I want Devel::Peek, not Scalar::Util

[reply]