Subject Re: UNICODE_FSS in select statement - ERROR
Author Sasa Mihajlovic
Hi,

> It's needed, in order for the engine to substitute the 3-byte UNICODE_FSS code sequence for the 1-byte Win1251 code sequence for each character...otherwise, that statement would just throw "malformed string" errors.
>
> ./heLen
>

Is there any way to change collation on database or I must change all records which contain latin characters to ascii characters. There are few milion records in some tables and I have a big trouble with all LIKE statements?