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 explicit JOIN's) in the
same query

In our case, we're selecting from a stored procedure.

> existing debuggers is emulators and can't work exactly same way as
engine

Thank goodness for that otherwise we wouldn't have gotten this far :)

> v1.5 is not developed for a long time, consider upgrade

FB 2.5.2 is on the to-do list, which is now about twenty pages long :(

-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of hvlad
Sent: Wednesday, March 13, 2013 9:02 AM
To: firebird-support@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 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 explicit JOIN's) in the
same query, iirc.

> but works if the stored procedure is stepped through under the DBW 
> debugger.

  There is no native debuggers for Firebird. All existing debuggers is
emulators and can't work exactly same way as engine itself. Also, they
have own mistakes in implementation. So, don't trust debuggers blindly
:)

Regards,
Vlad

PS v1.5 is not developed for a long time, consider upgrade to the more
recent version...




------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Visit http://www.firebirdsql.org and click the Resources item on the
main (top) menu.  Try Knowledgebase and FAQ links !

Also search the knowledgebases at http://www.ibphoenix.com 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Yahoo! Groups Links



Reply via email to