Hi, 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). Backward compatibility is achieved by falling back to NONE when nothing is specified in the config. This change would allow Java and .NET clients default the connection charset to UTF-8 thus avoiding a situation when data is written in different charsets in heterogenous environments (e.g. Linux with default UTF-8 and Windows with default WIN1251). The change is proposed for Firebird 3.0. Roman Rokytskyy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
