06.07.2012 6:57, Dmitry Yemanov wrote: > 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.
How about isc_create_database()? Should it follow the same rules? > 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? 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. > 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? Yep: how to find out server version before creating database? -- 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
