On Fri, 06 Jul 2012 10:20:13 +0200, Dimitry Sibiryakov <[email protected]> wrote: > I have a script which creates my tables in my own just created database > or any existing > user-choosen database. Because I can't predict default character set of > such user > database, all fields in this script are created with explicit character > set NONE. > Proposed disabling of charset NONE will break this schema.
Ah, that makes sense. I actually think explicit use of NONE should not be prohibited at all (not even as the default character set of a database). Such an explicit decision indicates (or at least: it should indicate) that you know what you are doing and therefor Firebird should just let you do it and not try to babysit you. But the current situation where no explicit decision means NONE, actually means that Firebird simply hands you the shovel to dig your own grave while you think you are building a sandcastle ;) >>> > Yep: how to find out server version before creating database? >> Could you be more explicit about the problem you are expecting? > > The question is: what character set to use in creation script? An > attempt to create > database with charset UTF-8 fail on servers before FB 2.1. If attempt to > create database > with charset NONE will fail on servers after FB 3.0 - how to choose > character set for > CREATE DATABASE statement? Thanks for the explanation. Mark ------------------------------------------------------------------------------ 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
