> ><?xml version="1.0" encoding="UTF-16" ?>
>
> There's why.
>
> There's no way that the Firebird client charset or the default database
> charset can transliterate your search string, that is probably ANSI or,
> at best, UTF8 (depending on what your client and DB charsets are) into
> UTF-16 encoding to make it a valid search string for your data.
>
> What you can do is convert the search string to UTF-16 at the client
> somehow and pass it (possibly with a transforming function expression)
> as a literal. There are tools and components around that can do this
> conversion for you. I believe the Jaybird driver can be configured to
> do it automatically (ask on the firebird-java list if this is your
> environment); for others you will need to find out explicitly from the
> interface developers. It's worth an ask on firebird-tools, as well.
>
> Depending on how you're using the data, you could look into some
> converter for your incoming data and actually store it as UTF8. (If
> the default charset isn't UTF8 then make it an attribute of the blob
> field itself.) A blob filter could be helpful here, if you could write
> one, or find one ready-made.
>
> ./heLen

Helen, this is content, not a declaration of charset for the blob type.
the CONTAINING select works fine for me on a TEXT blob on NONE charset for
this content.
Alan