Permalink
Browse files

Update the documentation for the :autosave option

I've noticed a caveat with the :autosave option biting people before.
Questions arise about why they must explicitly save an associated object
in their own before_save callbacks. I've updated the documentation as
such to note to users that the :autosave callback occurs before any
user defined callbacks. They must save the associated record themselves
if altering it in their own callbacks.

Signed-off-by: David Celis <david@davidcelis.com>
  • Loading branch information...
1 parent 891043d commit 230d7f760030c3400b682e4d8ffa1292ac1a9682 David Celis committed Aug 23, 2012
Showing with 3 additions and 1 deletion.
  1. +3 −1 activerecord/lib/active_record/associations.rb
@@ -1137,7 +1137,9 @@ module ClassMethods
# [:autosave]
# If true, always save the associated objects or destroy them if marked for destruction,
# when saving the parent object. If false, never save or destroy the associated objects.
- # By default, only save associated objects that are new records.
+ # By default, only save associated objects that are new records. This option is implemented as a
+ # before_save callback. Because callbacks are run in the order they are defined, associated objects
+ # may need to be explicitly saved in any user-defined before_save callbacks.
#
# Note that <tt>accepts_nested_attributes_for</tt> sets <tt>:autosave</tt> to <tt>true</tt>.
# [:inverse_of]

0 comments on commit 230d7f7

Please sign in to comment.