Helen Borrie wrote:

>At 02:19 AM 10/02/2005 +0000, you wrote:
>
>
>
>>But what encoding form does UNICODE_FSS use, or rather what encoding
>>should I pass to DSQL API functions, UTF-8? That can take up to 6 bytes!
>>
>>
>
>Don't pass unicode at all. Pass characters - whatever the user's keyboard
>mapping throws at the client. The client's lc_ctype setting will take care
>of the UNICODE_FSS conversion if it and the database are set up for it. If
>not, i.e. the database column is fss_unicode but the client and database
>are not, you face extra work (introducers or casting) to pass the locale
>strings in such a way that the engine is able to do that bridge work.
>
>

So if I specify lc_ctype as "UTF-8" I'm safe? (assuming I want to pass
UTF-8 form data of course)

Scott