On Fri, 28 Mar 2014 16:28:40 +0100, Dimitry Sibiryakov <s...@ibphoenix.com> wrote: > 28.03.2014 16:23, Adriano dos Santos Fernandes wrote: >> The only problem would be old server accessed with new client and >> message file. > > Exactly because of this old messages must not be changed this way, new > messages must be > added instead.
I disagree (and btw: 'incompatible' changes to messages have happened before). The errorcodes themselves are in my opinion more part of the Firebird API than the messages themselves. If I receive error code 335544558 (isc_check_constraint) I know it is a check constraint violation. If part of my code depends on knowing that, I don't want to discover that in a next version of Firebird I need to *also* check for 347182760 (isc_check_constraint_v2)(to name a random non-existent error code). Now if I also need to parse the message or the status vector then I do have a problem on my hands, but that problem remains localized to a single error code (and I might already have fallback handling in place for parse failures). Mark ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
