From 1b898cc946f69808d5fa0db922ba100fb8ffcfe3 Mon Sep 17 00:00:00 2001
From: Xavier Noria <fxn@hashref.com>
Date: Sun, 2 May 2010 00:47:09 +0200
Subject: say something about after_(commit|rollback) in callbacks.rb, the fact
 that their implementation is elsewhere is not important for rdoc purposes

---
 activerecord/lib/active_record/callbacks.rb | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

(limited to 'activerecord/lib/active_record/callbacks.rb')

diff --git a/activerecord/lib/active_record/callbacks.rb b/activerecord/lib/active_record/callbacks.rb
index 98c14e6eb0..7ebeb6079e 100644
--- a/activerecord/lib/active_record/callbacks.rb
+++ b/activerecord/lib/active_record/callbacks.rb
@@ -17,8 +17,13 @@ module ActiveRecord
   # * (-) <tt>create</tt>
   # * (5) <tt>after_create</tt>
   # * (6) <tt>after_save</tt>
+  # * (7) <tt>after_commit</tt>
   #
-  # That's a total of eight callbacks, which gives you immense power to react and prepare for each state in the
+  # Also, an <tt>after_rollback</tt> callback can be configured to be triggered whenever a rollback is issued.
+  # Check out <tt>ActiveRecord::Transactions</tt> for more details about <tt>after_commit</tt> and
+  # <tt>after_rollback</tt>.
+  #
+  # That's a total of ten callbacks, which gives you immense power to react and prepare for each state in the
   # Active Record lifecycle. The sequence for calling <tt>Base#save</tt> for an existing record is similar, except that each
   # <tt>_on_create</tt> callback is replaced by the corresponding <tt>_on_update</tt> callback.
   #
-- 
cgit v1.2.3