On Fri, 06 Jul 2012 09:45:06 +0200, Dimitry Sibiryakov <s...@ibphoenix.com> wrote: > How about isc_create_database()? Should it follow the same rules?
It probably should. >> 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. 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? The use of different charactersets for individual columns has its uses. >> 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? Could you be more explicit about the problem you are expecting? 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
