Changing the catch block:
WHEN /*GDSCODE unique_key_violation*/ ANY DO
Allows us to work around the problem.
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 kind of JOIN syntax (implicit and
I see the exception no current record for fetch operation all the time
when dealing with stored procedures so I ignore it. Perhaps it's an
issue with FB 1.5.
-Original Message-
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of hvlad
Sent:
I think it's a 1.5 bug, as executing the procedure from DBW also fails
but works if the stored procedure is stepped through under the DBW
debugger.
-Original Message-
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of hvlad
Sent: Sunday, March
