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 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:
>
> EXECUTE PROCEDURE P_IMPORT;
>
> Yields this error:
>
> Statement failed, SQLCODE = -508
> no current record for fetch operation
> -violation of PRIMARY or UNIQUE KEY constraint

I'd said the error is not "violation of PRIMARY or UNIQUE KEY
constraint" but "no current record for fetch operation".
I don't know why second (wrong) part is there...

Regards,
Vlad



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

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

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