On 28/04/2011 08:20, Geoff Worboys wrote: > Adriano dos Santos Fernandes wrote: > ... >> Data is transliterated from its charset to client charset and >> vice-versa. > NONE/OCTETS ->> something: data is validated accordingly to something > something ->> NONE/OCTETS: nothing is done > something1 ->> something2: data is transliterated > > > Hi Adriano, > > 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.
> There would appear to be potential complications with literal > cast requests (eg: _ISO8859_1'abc') in connections using other > UTF8 or other character sets etc. (Wondering if the client > interface is expected to deal with such things - when asking > for user input - or whether the server handles them in some > vaguely sensible way (I suspect there is not always a good > solution).) > In 2.5 the problems with introducer is fixed transforming the string (in memory for monitoring and in metadata) to x'HEXSTRING', so it's always ASCII-compatible. 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
