On Wed, 24 Feb 2016 16:43:25 +0100, Dimitry Sibiryakov <s...@ibphoenix.com> wrote: > 24.02.2016 16:20, Dmitry Yemanov wrote: >> If some 3rd party drivers rely on these numbers, we may >> keep supporting them longer. > > Well, all versions of IBPR will stop working if isc_sqlcode() do. > > 24.02.2016 16:29, Mark Rotteveel wrote: > > So you should switch to SQLstate, or use the firebird > > error codes (aka gdscode) directly and map to the error messages in a > > similar way that drivers like Jaybird and Firebird .net provider do. > > In fact, it means parsing whole status vector because primary error > codes in most cases > are useless.
I think parsing the status vector is a must anyway, and the error code in my opinion are less "useless" than the SQLCODE, as a lot of error codes at least point to a specific problem (and the ones that have a very generic first error code nicely map to the extremely broad SQLCODE like -104 or -901), which can't be said about SQLCODE. Mark ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
