|
I'm looking for a way to create a trigger function that gets
called once per transaction as an AFTER EVENT.
Because there is no option for creating such
a trigger function I was looking at the "create constraint trigger"
command.
My approach would be to check the current transaction id to
ensure that I only execute the function once per transaction and if it
was deferred it would happen at the end of the transaction which
would simulate an AFTER EVENT.
Apart from the obvious backup and restore problems can anyone
think of any undesired side effects if I used this command?
Thanks in advance,
Donald Fraser
|
