Re: [Firebird-devel] Status of SQLCODE

On 24/02/16 16:25, Mark Rotteveel wrote: > On Wed, 24 Feb 2016 16:43:25 +0100, Dimitry Sibiryakov > 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

Re: [Firebird-devel] Status of SQLCODE

On Wed, 24 Feb 2016 16:43:25 +0100, Dimitry Sibiryakov 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. > >

Re: [Firebird-devel] Status of SQLCODE

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

Re: [Firebird-devel] Status of SQLCODE

On Wed, 24 Feb 2016 11:28:07 +, Lester Caine wrote: > I'm finally taking the time to push the improved Firebird driver for > ADOdb in PHP over to the new development home for that project and one > of the things I decided to tidy up is the error messages which still >

Re: [Firebird-devel] Status of SQLCODE

24.02.2016 14:28, Lester Caine wrote: > I'm finally taking the time to push the improved Firebird driver for > ADOdb in PHP over to the new development home for that project and one > of the things I decided to tidy up is the error messages which still > relate to the original FB1 list. Currently

[Firebird-devel] Status of SQLCODE

I'm finally taking the time to push the improved Firebird driver for ADOdb in PHP over to the new development home for that project and one of the things I decided to tidy up is the error messages which still relate to the original FB1 list. Currently ADOdb takes the shorthand SQLCODE and provides