[Mikel]

DonQuichote wrote on Mar 30 2007, 08:41 AM:

Ah. There's the little bug. I used mysqldump to dump the table and it shows “€ 5” when viewed as unicode. All settings (during dump and for the server) point to utf-8, so there is really a storage problem in MySQL.

Thanks for helping me out.

For other people having the same problem:

I configure both the server (mysqld section) and the client (mysql section) in the my.ini file to use utf-8. However, this affects the server only and does NOT set the default encoding for a client connection. So the connections I opened from PHP defaulted to latin-1. SQLyog did not show this problem, as it sends a SET NAMES statement upon opening a connection. What is even more troubling is that this seems to affect modern (5.0) versions of MySQL only. And pre-4.1 versions do not even understand the SET NAMES command. Trying to stay compatible with different versions really gets hard this way…

So the solution is checking the MySQL version and sending the appropriate SET NAMES command if the version is >4.1.

Thanks a lot for this solution, it works great and stopped me from ripping my hair out trying to work out why I kept getting question marks instead of my utf-8 data! Now if only PHP supported UTF8 natively too…. :huh: Well hopefully not too long till PHP6 now anyway 😉

[Author]

Posts