Bug #17643 Erron in sql
Submitted: 22 Feb 2006 12:11 Modified: 23 Mar 2006 10:30
Reporter: Devendra Chipte Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version: OS:
Assigned to: CPU Architecture:Any

[22 Feb 2006 12:11] Devendra Chipte
Description:
Hi there,
I have been using PHP and mysql since last 5 years I have never got
this problem, I am just trying to execute a simple query that is

SELECT * FROM `clients` WHERE client_name='Asus'
but it gives me an error it says:

#1267 - Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='

for your reference here are my server details:

Php                             4.3.9
Phpmyadmin                 2.6.1.pl3
Mysql                         4.1.7
Apache                    2.0.52

If you can give me any sort of advice or help in this regard, i'd be
able to go further with this. I've been stuck at this point for the
last week or so, and it's been very frustrating to say the least.
Please spare a moment and help a brother out.

Sincerely,
Devendra

How to repeat:
Is there any specific reason or I hve dont something wrong during installation. is there any option where I can disable this Collations thing permanently
[23 Feb 2006 10:11] Valeriy Kravchuk
Thank you for a problem report. Please, send the SHOW CREATE TABLE `clients` and SHOW VARIABLES LIKE 'char%' results from the environment you used to run that SELECT (PHP?).
[23 Feb 2006 10:24] Devendra Chipte
Thanks for you reply 
here are are the print screens I have upladed for your reference

http://www.dit.net/sho_create_table.gif

http://www.dit.net/show_varialbe.gif
 
Thanks & Reg.,
Devendra
[23 Feb 2006 10:30] Valeriy Kravchuk
Please, try to execute

set names latin1;

before your SELECT, then run SELECT and inform about the results.
[24 Mar 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".