![]() Then you don’t want to use the on_commit() hook. If it’s not (if your follow-up action is soĬritical that its failure should mean the failure of the transaction itself), For the intended use cases (mail notifications, background ![]() They are executedĬonditionally upon the success of the transaction, but they are not part of Your callbacks are executed after a successful commit, so a failure in aĬallback will not cause the transaction to roll back. Savepoints, even for the outermost block. You may use atomic when autocommit is turned off. The overhead of savepoints is noticeable. If there is one, and the outermost block otherwise. Perform the rollback when exiting the first parent block with a savepoint You can disable the creation of savepoints for inner blocks by setting the commits or rolls back the transaction when exiting the outermost block.releases or rolls back to the savepoint when exiting an inner block. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |