>After the original "Problem with CONTAINING and COLLATE" thread I

switched to UTF8 but not happy with it.

>The optional COLLATE after CONTAINING have no effect, the database

default COLLATION used. See the below

>examples. Tried with 3.0.3.32854 snapshot and Linux 64bit (Ubuntu

14.04.1).

<table definition and good examples skipped>

Why would you want collate AFTER containing? I must admit I haven't
tried your queries in Fb 3.0 (I'm still on 2.5), but I'd say the
sensible way to specify what you want, would be

SELECT * FROM TABLE1 WHERE NAME COLLATE UNICODE_CI_AI CONTAINING 'o';
//returns four rows on an old 2.5 installation

and not

SELECT * FROM TABLE1 WHERE NAME CONTAINING 'o' COLLATE UNICODE_CI_AI;
//gives a 'data type unknown' error message

I read your statement as "'o' COLLATE UNICODE_CI_AI", not the entire
where clause being told to use that collation. Though, as I said, I
don't have Fb 3.0 on this computer and don't know whether or not Fb
agrees with me.

HTH,
Set