Rafal Pietrak wrote:
> I'd like to propose a 'syntax/semantics' of such trigger:
>
> Triggers normally execute inside of a transaction.
>
> A COMMIT within a trigger could mean: "do a fork: fork-1) return to the
> main and schedule COMMIT there, fork-2) continue in bacground".
>
And what if fork-1) returns to the main, attempts the COMMIT but instead and rolls back due
to a violated constraint? Where does that leave fork-2?
Regards,
Thomas Hallgren
