🚀 go-pugleaf

Martijn Tonies wrote:

> Patrick, try:
> 
> when gdscode lock_conflict do
> 
> It's the normal isc_ code, without the isc_ part.

AMAZING!!! How would you ever think to specify only part of the
documented code?
And, who would ever make something work like this?  Anybody from
Codegear feel free to jump in here!
Anyway, this saves (compiles) the stored procedure. No error for
unknown identifier. But I can't tell how it's working.
If I say WHEN ANY and write out a test string my error is trapped and
the test string writes out.  If I say WHEN GDSCODE exception_name, my
error is trapped, but the test string doesn't write out. I know I get
an IB Exception Message without the WHEN, but I'm not sure what
GDSCODE, if any, is actually being thrown. I thought this last would
trap only that one code. So, I'm not sure how well IB is even working
with this.
Any idea how to identify the error that the When statement is
receiving?, or the associated message.
Even if I can get this to work, I need the error message.

-- 
Patrick Moloney