Hi! Implicit charset of parameters in EXECUTE BLOCK works different in v2.5 and v3 and IMO both are incorrect.
v2.5: a) If the connection charset is NONE, parameters are described with the database charset. This is wrong cause the database charset is a concept related to stored metadata. b) If a connection charset is used, (a) is done too, but then are converted again and described with the connection charset. This is not a wrong rule, but wrong when (a) is done and the database charset is not NONE. v3: a) If the connection charset is NONE, parameters are described as NONE. This is correct. b) If a connection charset is used, parameters are described with the connection charset. This is wrong, NONE should continue as NONE. So I propose that: a) metadata charset is not taken into account in EXECUTE BLOCK and b) that normal (NONE->ANYTHING = NONE; ANYTHING->NONE = ANYTHING; ANYTHING->NON-NONE-CS = NON-NONE-CS) conversion rules are used. Adriano ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
