Re: [Firebird-devel] UTF8 Encoding and Decoding

[Geoff W. <ge...@te...>]

Adriano dos Santos Fernandes wrote:
> On 28/04/2011 08:20, Geoff Worboys wrote:
>> ...
>> While on this sort of subject are you able to offer any
>> information about what happens to API text such as SQL
>> statements and the like) sent to the server?  (And details
>> like relation names etc returned to the client.)
>>
> They're interpreted in the client charset and converted (by
> rules above) to unicode_fss for storage.

I see the FB v2.5 release notes mention: "Malformed characters
are no longer allowed in data for UNICODE_FSS columns." which
answers my first followup question.  So according to the rules
a client connection of NONE should be sending SQL statements
compatible-with/able-to-be-validated-as UNICODE_FSS.

For most purposes we can, at the client, assume UNICODE_FSS
is the equivalent of UTF8, yes?  Are there any client side
distinctions we should be aware of?

Thanks for your help, Adriano.

-- 
Geoff Worboys
Telesis Computing