On 28/04/2011 08:57, Geoff Worboys wrote: > 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? > Yes. But UNICODE_FSS is currently validated as UTF-8 but in fact it should not allow 4-bytes characters. So doing it may result in problems when converting from UNICODE_FSS to UTF-8 or other character set.
It's better to never use NONE charset, specially for the connection charset. Adriano ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
