Bug #10446 Illegal mix of collations

Description:
when i'am trying to write a simple query like
select * from t where id=lapd('xxx',10.' ')
it runs good from the command line but from the browser i get the following:
Error 'Illegal mix of collations (utf8_bin,IMPLICIT) and (latin1_swedish_ci,NONE)
please check for the problem.
while using older version on thr browser it worked just good

How to repeat:
yaniv.eylon@flectronics.co.il

Hi,

I was unable to reproduce this bug, can you please tell me what the steps to reproduce it are ?

Thanks !

Hi Jorge,
well all i can add to what i rowte last time is create any simpale DB with MyIsam TBL and write a simple query like i worte : select * from t where id=lapd('xxx',10.' ')
it gives the folowing aswer : Error 'Illegal mix of collations (utf8_bin,IMPLICIT) and
(latin1_swedish_ci,NONE)
i hopr this will help you go on (on the unix version it workes just fine)
have a nice day & sorry for the delay Yaniv

I was able to reproduce on MySQL 4.1.13, Win 2000 SP4
Error message:
Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='
Charset variables:
+--------------------------+-------------------------+
| Variable_name            | Value                   |
+--------------------------+-------------------------+
| character_set_client     | latin1                  |
| character_set_connection | latin1                  |
| character_set_database   | latin1                  |
| character_set_results    | latin1                  |
| character_set_server     | latin1                  |
| character_set_system     | utf8                    |
| character_sets_dir       | E:\data\share\charsets/ |
+--------------------------+-------------------------+

MySQL Query Browser 1.1.9

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/27248

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/32455

Fixed in 4.1.16 and 5.0.17

Noted in 4.1.16, 5.0.17 changelogs.