Larry Leeth
New Member
I would like be able to pass information from an executing procedure to any DB triggers activated by that procedure.
The main problem, as I see it, is that multiple procedures may be active in a given user session - any of which may fire a given DB trigger. When a trigger fires, I want to know which procedure caused if to fire.
I can 'walk-the-widget-tree', or procedure stack, to see what procedures are active, but how can I determine the triggering procedure from within the logic of a DB trigger?
If I could pass info to the DB trigger, I could set a 'global-unique-ID' (GUID) in the top-level procedure and communicate the GUID to the trigger.
Any suggestions?
The main problem, as I see it, is that multiple procedures may be active in a given user session - any of which may fire a given DB trigger. When a trigger fires, I want to know which procedure caused if to fire.
I can 'walk-the-widget-tree', or procedure stack, to see what procedures are active, but how can I determine the triggering procedure from within the logic of a DB trigger?
If I could pass info to the DB trigger, I could set a 'global-unique-ID' (GUID) in the top-level procedure and communicate the GUID to the trigger.
Any suggestions?
