Re: #HY000Illegal mix of collations for operation 'concat'
Posted by: Reggie Burnett
Date: November 09, 2004 03:59PM

It's not that it can't handle the latin1 character set. The problem is that you get into trouble when comparing columns and literals of different character sets. Your tables were latin1 and the SQL was being sent over as utf8.

I have just committed some code that should help with this issue. Beginning with 1.0.2, you will be able to specify that character set that should be used to send all queries to the server. If all your tables are latin1, then you can add charset=latin1 to your connection string and avoid the utf8->latin1 conversion.

I am planning on writing an article for the MySQL dev zone that will clarify this point somewhat so you should watch for that.


Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.