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
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.
>
>
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
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
>
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
ok, sorry I did not understand.
I found the source of a new VM and it compiles under lazarus 3.0 good
:-)
Carlos H. Cantu a écrit :
> Currently Firebird.pas can be found only in the linux builds.
> That's what Alex is talking about. It should be on Windows builds too.
--
Norbert Saint Georges
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
On 02/24/2016 12:13 AM, Vlad Khorsun wrote:
> PS If you need it so much, i offer to apply patch but disable #line
> generation for release build in public
> source tree.
Or keep this:
-case IN_SW_GPRE_N:
-sw_lines = false;
-break;
And have different sw_lines for