Re: [Firebird-devel] PROPOSAL FB 3.0: Ditch the NONE as default charset

[Adriano d. S. F. <adr...@gm...>]

On 05/07/2012 09:50, Stefan Heymann wrote:
>> After some hot discussion in Firebird-Java, I want to propose to ditch
>> the NONE as default character set for newly created databases when no 
>> database charset is specified.
>> The server/engine should read the config file and use the default 
>> character set which is specified there. The installer asks for this 
>> character set during installation and defaults the selection to the 
>> current character set of the environment (regional settings on Windows,
>> LANG/LC_CTYPE environment vars on Linux).
> Why not make the DEFAULT CHARACTER SET clause required? So everybody
> who creates a database *must* define one and make sure it's the right
> one.
>
>> 1.2.Example: 2 weeks ago i was told that Firebird only supports
>> KOI8-R for Russian. I was kind of speechless.
> Firebird also supports ISO8859_5 and WIN1251 for Cyrillic characters.
> But for KOI8-R there seems to be a collation for Russian (same for
> KOI8-U).
>
>> 2.2.1 FB project is to have a policy how clients are to deal with character
>> sets.
> The specified behaviour for all character sets except NONE and OCTETS
> is
>
>     Client <--- Unicode ---> Server
>
> (whenever there is a difference between the client and the server CS).
> Transliteration is always done by the Firebird client library.

It's done by the engine (server).


Adriano