06.07.2012 9:54, Mark Rotteveel wrote: >> > Shouldn't it be coupled with prohibiting declaration of charset for >> > single fields? >> >Currently nothing prevent (me) from creating database with default > charset >> >NONE and set >> >charset for every character field in every table. > I am not sure I see why you would need to prohibit setting the > characterset of a specific field when requiring the default characterset to > be set. Could you explain the reasoning on that?
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. >> > 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? -- WBR, SD. ------------------------------------------------------------------------------ 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
