Re^3: Encoding issue from DBI to string

Even after adding in the default-collation=utf8_unicode_ci, I'm still getting all question marks for multibyte characters. What a headache.

Not sure if anyone who have the answer here, but assuming the DB is set up appropriate with all UTF-8 encoding and data appearing valid in the tables, it wouldn't really matter how it's getting into the database to begin with, right?

We're using a 3rd party program as a scraper, and its underlying Java is dumping the data to the DB. I haven't looked into it much just because the data appears right in the DB with all UTF-8 encoding configured, so I assumed it wasn't the issue.

Comment on Re^3: Encoding issue from DBI to string Download Code

Replies are listed 'Best First'.
Re^4: Encoding issue from DBI to string by karlgoethebier (Abbot) on Jan 04, 2013 at 10:02 UTC
"Even after adding in the default-collation..." S*t! "...it wouldn't really matter how it's getting into the database to begin with, right?* To be honest, i'm not shure about this. BTW, what happens if you fire up your query using mysql client? Regards, Karl ŤThe Crux of the Biscuit is the Apostropheť	[reply]