提交 37054e6e 编写于 作者: X Xavier Noria

documented how to trigger rollbacks within the callback chain, and related gotchas

上级 fcdf8e29
......@@ -172,7 +172,16 @@ module ActiveRecord
#
# == Transactions
#
# The entire callback chain for +save+ and +destroy+ runs within their transaction.
# The entire callback chain for +save+ and +destroy+ runs within their transaction, including
# the <tt>after_*</tt> hooks. Cancellation does not trigger a rollback. To rollback
# the transaction just raise an exception the same way you do for regular transactions.
#
# Note though that such an exception bypasses the regular call chain in Active Record:
# If ActiveRecord::Rollback is raised both +save+ and +destroy+ return +nil+. On the other
# hand <tt>save!</tt> does *not* raise ActiveRecord::RecordNotSaved, and does not raise
# anything else for that matter, <tt>save!</tt> just returns +nil+ in that case.
# If any other exception is raised it goes up until it reaches the caller, no matter
# which one of the three actions was being performed.
module Callbacks
CALLBACKS = %w(
after_find after_initialize before_save after_save before_create after_create before_update after_update before_validation
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册