--- In firebird-support@yahoogroups.com, "Rick Debay" wrote:
>
> Changing the catch block:
> WHEN /*GDSCODE unique_key_violation*/ ANY DO
> Allows us to work around the problem.
This is not a mine deal of course, but this is VERY BAD. Hiding exceptions is
a *very bad* practice. But this is you
port@yahoogroups.com
Subject: [firebird-support] Re: Catching exception fails under isql
--- In firebird-support@yahoogroups.com, "Rick Debay" wrote:
>
> I think it's a 1.5 bug, as executing the procedure from DBW also fails
"no current record for fetch" is we
--- In firebird-support@yahoogroups.com, "Rick Debay" wrote:
>
> I think it's a 1.5 bug, as executing the procedure from DBW also fails
"no current record for fetch" is well-known optimizer bug and in some form
exists even in latest Firebird versions. Usually it happens when one mixed two
ki
ch 10, 2013 4:23 AM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Re: Catching exception fails under isql
--- In firebird-support@yahoogroups.com, "Rick Debay" wrote:
>
> Does anyone have any insight in to this?
>
> Running this statement in isql:
>
f Of hvlad
Sent: Sunday, March 10, 2013 4:23 AM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Re: Catching exception fails under isql
--- In firebird-support@yahoogroups.com, "Rick Debay" wrote:
>
> Does anyone have any insight in to this?
>
> Running t
--- In firebird-support@yahoogroups.com, "Rick Debay" wrote:
>
> Does anyone have any insight in to this?
>
> Running this statement in isql:
>
> EXECUTE PROCEDURE P_IMPORT;
>
> Yields this error:
>
> Statement failed, SQLCODE = -508
> no current record for fetch operation
> -violatio
