Pavel Stehule <[EMAIL PROTECTED]> writes:
> What it is mean?
I think it means Oracle is broken ;-)
> So we can have only one procedure level scope variable, which is
> initialized on start of exception and zeroized on the end of exception
> block. This behavior is different from my patch, but is better for Oracle
> compatibility and I prefere its.
That might be taking the notion of bug-compatibility with PL/SQL
a bit too far. For that matter, did you check whether Oracle
actually treats it as a procedure-scope variable? Try having the
exception block call another function and trap an error inside that.
Does SQLCODE change in the calling function?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
