MySQL Bugs: #7572: query unicode doesnot work

Bug #7572	query unicode doesnot work
Submitted:	29 Dec 2004 14:07	Modified:	31 Jan 2005 21:16
Reporter:	George Kyrolos	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.8	OS:	Windows (Win 2000 pro)
Assigned to:		CPU Architecture:	Any

Description:
i seared the  Bugs DB  fro a  problem like mine
here it is
i  was using mysql 4.0.22 , my tables are innodb
and the charachter set was latin
my application in VB6 sends a text data to tables 
like this one
Authors tables
Field                         Type                         Null
Auth_name               VarChar(100)           Not null
country                    Varchar(50)            Not null

i can send Arabic and English to the auth Name
when i tried to implement an AutoComplete system which is based on a select command
"select from authors where auth_name like '" & textbox.text & "%'"
i got shocked when i write in the textbox an arabic  character
and find the result of the select query  only "O" character !!!!!!!!!
and so on

here is an example when i was debuging step by step

select from authors where autH_name like '&#1588;%'
now the recordset!auth_name = "O"

im using odbc 3.51 
Ado 2.5

i read in ur bug db that  4.0.22 is not working good in the  context of  unicode characters
so i  upgraded to 4.1.8 and i found the same behavior

also  NOT LIKE  MS server 2000
i cannot  search for  mixed column values
i mean in in a CERTAIN row i have  some arabic  characters and others in english
it doesnot  work at all

thx

How to repeat:
try to fill a certain table with arabic or chinese characters and then try to search for those chinese values

Suggested fix:
MS sql server
pretending to write the letters as i entered them from left to right ( even if it is arabic) so im sure of the results in Sql Server

Please correct me if I understood wrong: are you want to retrieve a
select over one column which contains mixed characters English/Arabic ?

Thank you in advance.

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".