NexusDB

SQL triggers are always executed with an active transaction. For any insert/delete/update the core engine will start an implicit transaction before any extenders are notified about the event. SQL triggers are executed inside extender notifications and as such execute in the context of this implicit transaction. The core engine will commit this implicit transaction only if no error was raises in any of the extenders or during the execution of the insert/delete/update, otherwise it will be rolled back.