>Hi,
>How to handle error in nested stored procedure?
>IOW, How to know the trigger2 failed in trigger1?
>
>Thank you
Error handling in stored procedures has been quite a problem for me. The problem I had is that an error occurs, I click on "Suspend", but the debugger window won't show the source code. To show the executed code in the debugger, I had to explicitly put a SET STEP ON in the stored procedures, or set a breakpoint on the function name (
before the error occurs).
I guess you just have be more careful than usually when designing stored procedures, test them thoroughly, and try to consider everything that might go wrong, testing for these conditions in your code.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
