Jason Wharton wrote:

>> So, I haven't looked at the new IBO yet, but is a "sql statement" now
>> fully unicode? Or AnsiString?
>>
>
> The API doesn't appear to allow unicode strings yet. If it does I am not
> aware of it.
> My guess is they will have new API calls that are unicode compliant rather
> than making the existing AnsiString based calls switch over.
>
> Jason

...again, from firebird-support:

Thread name: Can I pass unicode SQL to Firebird API?

Chau Chee Yang wrote:

> > Hi,
> >
> > As firebird 2.0 supports UTF-8 charset, I am just wondering if the
> > firebird API function (eg: isc_dsql_prepare) can accept unicode SQL
> > statement:
> >
> > SELECT * FROM Table WHERE Field1="a utf-8 value"
> >
> > Best Regards,
> > Chau Chee Yang
> >
>

Well...

If it would not accept how would you store and search values ????

see you !

-- Alexandre Benson Smith Development THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil www.thorsoftware.com.br



-----8<----------8<----------8<----------8<-----

...and Helen's answer:

At 12:50 2/10/2008, you wrote:

> >Hi,
> >
> >As firebird 2.0 supports UTF-8 charset, I am just wondering if the
> >firebird API function (eg: isc_dsql_prepare) can accept unicode SQL
> >statement:
> >
> >SELECT * FROM Table WHERE Field1="a utf-8 value"
>

Yes, if
1) the search argument is well-formed; and
2) both the client character set (lc_ctype) and the character set of the searched column are of a fully compatible character set, i.e. both UTF8, or both of a charset to which it is possible to transliterate your UTF8 argument.

./heLen

-----8<----------8<----------8<----------8<-----

HTH,

m. Th.