Using a CONTAINING in a collumn with WIN1252 collate breaks with "Cannot transliterate character between character sets" [CORE4546] #4864
Submitted by: Fabio Gomes (fabioxgn)
Relate to CORE5202
After upgrading to 2.5.3 from 2.5.2 using a CONTAINING clause in some columns with some "invalid" characters started to break with "Cannot transliterate character between character sets".
Example data which breaks: AhÃƒÂº
The following breaks on 2.5.3 but works fine on 2.5.2, returnig "AhÃƒÂº";
Specifying the collate works on 2.5.3:
But if I use WIN1252 it breaks.
Is this a bug? It was working just fine on 2.5.2 without specifying the collate.
The text was updated successfully, but these errors were encountered:
Commented by: Geoff Worboys (gworboys)
An alternative example to work from:
Or see these:
From my post on the forum:
As far as I can tell (doing a test against all 256 characters) 0x83 is the only character in WIN1252 with the problem.
Note that WIN1253 also has a similar problem (I don't use it so didn't investigate the specifics).
To solve this in my own FB build I just added a mapping from U+0191 to 0x83 for WIN1252 - but I don't know if this is considered acceptable to a wider audience because presumably it would mean that WIN1252 would accept U+0191 in all transliterations (not just Upper of existing data) which may not be desirable (but is not important to my application).