06.07.2012 11:54, Mark Rotteveel wrote: > 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 believe his was referring to the default charset being set to e.g. UTF8 but some field would override it with NONE. I.e. it's only about NONE for fields, not about field specific declarations in general. Dmitry ------------------------------------------------------------------------------ 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
