Subject Re: Stored procedure return_value always null
Author flipmooooo
>
> That's why you should use an external table for logging if you
want the log
> to survive an unhandled exception. Writes to an external table
don't get
> undone by a rollback.
>
> ./hb

Hi,

No, it don't have to be that way. The way i do it inserting in SP1
it will survive the exception because it is done in the when clause
eating up the custom exceptions i want to respond too. If it's some
other exception that i don't respond too it won't be logged
(inserted) and doesn't need to be because SP1 will be exitted and
client will get the exact errormessage. My point is why isn't there
an 'exception_message' object that contains the used messagetext
related to the exception that occurred, just like the 'exception'
object. It's there somewhere (because the client will get the exact
message back incase of a non handled exception) but u just can't
reference it nowhere inside the SP. Would be alot nicer then to have
to refer to external tables. Just my two cents.

Greetings,
Filip Moons