Simulating Trigger On COMMIT
Hi,
We have multiple tables that get updated as part of a transaction. After all the data is added succesfully there is processing that needs to be done, so we'd like to use a trigger to kick it off automatically.
I thought of attaching a trigger to the master table but I can't find an approach or mechanism that would allow us to defer the triggered code until after all the tables have been updated.
It almost seems like I want a transaction trigger. Something that would be executed before or after a COMMIT. But the post-processing code does not have to be deferred until after the transaction is committed, it just mustn't be started until all the tables participating in the transaction have been updated, otherwise all the data needed won't be present.
I thought of attaching a trigger to the master table but I can't find an approach or mechanism that would allow us to defer the triggered code until after all the tables have been updated.
It almost seems like I want a transaction trigger. Something that would be executed before or after a COMMIT. But the post-processing code does not have to be deferred until after the transaction is committed, it just mustn't be started until all the tables participating in the transaction have been updated, otherwise all the data needed won't be present.
0