diff options
| author | Vijay Dev <vijaydev.cse@gmail.com> | 2012-10-21 18:23:29 +0530 |
|---|---|---|
| committer | Vijay Dev <vijaydev.cse@gmail.com> | 2012-10-21 18:23:50 +0530 |
| commit | e84281398e79e09b637c888860fcefd6f82bf968 (patch) | |
| tree | a1320d280f48a772e1f4696c999e6a44d40752e1 /activerecord/lib/active_record/callbacks.rb | |
| parent | c9a88a2c26a0d9050e6106ef5e0617fe5c4cca24 (diff) | |
| download | rails-e84281398e79e09b637c888860fcefd6f82bf968.tar.gz rails-e84281398e79e09b637c888860fcefd6f82bf968.tar.bz2 rails-e84281398e79e09b637c888860fcefd6f82bf968.zip | |
copy edits [ci skip]
Diffstat (limited to 'activerecord/lib/active_record/callbacks.rb')
| -rw-r--r-- | activerecord/lib/active_record/callbacks.rb | 21 |
1 files changed, 7 insertions, 14 deletions
diff --git a/activerecord/lib/active_record/callbacks.rb b/activerecord/lib/active_record/callbacks.rb index 9626df08aa..3aabf3b3f2 100644 --- a/activerecord/lib/active_record/callbacks.rb +++ b/activerecord/lib/active_record/callbacks.rb @@ -203,14 +203,12 @@ module ActiveRecord # == Ordering callbacks # # Sometimes the code needs that the callbacks execute in a specific order. For example, a +before_destroy+ - # callback (log_children in this case) should be executed before the children get destroyed by the - # dependant destroy option. + # callback (+log_children+ in this case) should be executed before the children get destroyed by the +dependent: destroy+ option. # - # Let's take at the code below: + # Let's look at the code below: # # class Topic < ActiveRecord::Base - # - # has_many :children, dependant: destroy + # has_many :children, dependent: destroy # # before_destroy :log_children # @@ -219,16 +217,13 @@ module ActiveRecord # # Some child processing # end # end - # # end # - # In this case the problem is that when the +before_destroy+ is executed, the children are not available - # because the dependant destroy gets executed first. To solve this issue it is possible - # to use the +prepend+ option on the +before_destroy+ callback. + # In this case, the problem is that when the +before_destroy+ callback is executed, the children are not available + # because the +destroy+ callback gets executed first. You can use the +prepend+ option on the +before_destroy+ callback to avoid this. # # class Topic < ActiveRecord::Base - # - # has_many :children, dependant: destroy + # has_many :children, dependent: destroy # # before_destroy :log_children, prepend: true # @@ -237,11 +232,9 @@ module ActiveRecord # # Some child processing # end # end - # # end # - # This way, the +before_destroy+ gets executed before the <tt>dependant: destroy</tt> is called, and - # the data is still available. + # This way, the +before_destroy+ gets executed before the <tt>dependent: destroy</tt> is called, and the data is still available. # # == Transactions # |