--- In [email protected], "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 your code and your life...
 
> > "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.

  Which have no statements inside, huh ?

Regards,
Vlad

Reply via email to