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

[Dmitry Y. <fir...@ya...>]

06.07.2012 8:37, Roman Rokytskyy wrote:
>
>> 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.
>
> Yes, this is also an option. Maybe even the easiest one.

Sure, although it's going to break an unknown number of user scripts. 
 From another side, those using NONE as default charset might deserve 
that ;-)

But if we'd go this route, one more idea comes to mind. What about 
prohibiting NONE as a default database charset at all, even if specified 
explicitly? Those who want to save on transliteration would still have 
that ability by matching the server and connection charsets or by using 
NONE as a connection charset. Does anybody see any problem here?


Dmitry