Regenerate Guides HTML

2 files changed, 70 insertions, 7 deletions

diff --git a/railties/doc/guides/html/association_basics.html b/railties/doc/guides/html/association_basics.html
index bfe8f3f341..0aaad5b5bd 100644
--- a/railties/doc/guides/html/association_basics.html
+++ b/railties/doc/guides/html/association_basics.html
@@ -791,6 +791,11 @@ http://www.gnu.org/software/src-highlite -->
 <div class="ulist"><ul>

 <li>

 <p>

+<tt>:autosave</tt>

+</p>

+</li>

+<li>

+<p>

 <tt>:class_name</tt>

 </p>

 </li>

@@ -840,6 +845,8 @@ http://www.gnu.org/software/src-highlite -->
 </p>

 </li>

 </ul></div>

+<h5 id="_tt_autosave_tt"><tt>:autosave</tt></h5>

+<div class="paragraph"><p>If you set the <tt>:autosave</tt> option to <tt>true</tt>, Rails will save any loaded members and destroy members that are marked for destruction whenever you save the parent object.</p></div>

 <h5 id="_tt_class_name_tt"><tt>:class_name</tt></h5>

 <div class="paragraph"><p>If the name of the other model cannot be derived from the association name, you can use the <tt>:class_name</tt> option to supply the model name. For example, if an order belongs to a customer, but the actual name of the model containing customers is <tt>Patron</tt>, you&#8217;d set things up this way:</p></div>

 <div class="listingblock">

@@ -1099,6 +1106,11 @@ http://www.gnu.org/software/src-highlite -->
 </li>

 <li>

 <p>

+<tt>:autosave</tt>

+</p>

+</li>

+<li>

+<p>

 <tt>:class_name</tt>

 </p>

 </li>

@@ -1165,6 +1177,8 @@ http://www.gnu.org/software/src-highlite -->
 </ul></div>

 <h5 id="_tt_as_tt"><tt>:as</tt></h5>

 <div class="paragraph"><p>Setting the <tt>:as</tt> option indicates that this is a polymorphic association. Polymorphic associations are discussed in detail later in this guide.</p></div>

+<h5 id="_tt_autosave_tt_2"><tt>:autosave</tt></h5>

+<div class="paragraph"><p>If you set the <tt>:autosave</tt> option to <tt>true</tt>, Rails will save any loaded members and destroy members that are marked for destruction whenever you save the parent object.</p></div>

 <h5 id="_tt_class_name_tt_2"><tt>:class_name</tt></h5>

 <div class="paragraph"><p>If the name of the other model cannot be derived from the association name, you can use the <tt>:class_name</tt> option to supply the model name. For example, if a supplier has an account, but the actual name of the model containing accounts is Billing, you&#8217;d set things up this way:</p></div>

 <div class="listingblock">

@@ -1467,6 +1481,11 @@ http://www.gnu.org/software/src-highlite -->
 </li>

 <li>

 <p>

+<tt>:autosave</tt>

+</p>

+</li>

+<li>

+<p>

 <tt>:class_name</tt>

 </p>

 </li>

@@ -1568,6 +1587,8 @@ http://www.gnu.org/software/src-highlite -->
 </ul></div>

 <h5 id="_tt_as_tt_2"><tt>:as</tt></h5>

 <div class="paragraph"><p>Setting the <tt>:as</tt> option indicates that this is a polymorphic association, as discussed earlier in this guide.</p></div>

+<h5 id="_tt_autosave_tt_3"><tt>:autosave</tt></h5>

+<div class="paragraph"><p>If you set the <tt>:autosave</tt> option to <tt>true</tt>, Rails will save any loaded members and destroy members that are marked for destruction whenever you save the parent object.</p></div>

 <h5 id="_tt_class_name_tt_3"><tt>:class_name</tt></h5>

 <div class="paragraph"><p>If the name of the other model cannot be derived from the association name, you can use the <tt>:class_name</tt> option to supply the model name. For example, if a customer has many orders, but the actual name of the model containing orders is <tt>Transaction</tt>, you&#8217;d set things up this way:</p></div>

 <div class="listingblock">

@@ -1953,6 +1974,11 @@ http://www.gnu.org/software/src-highlite -->
 </li>

 <li>

 <p>

+<tt>:autosave</tt>

+</p>

+</li>

+<li>

+<p>

 <tt>:class_name</tt>

 </p>

 </li>

@@ -2061,6 +2087,8 @@ http://www.gnu.org/software/src-highlite -->
   has_and_belongs_to_many <span style="color: #990000">:</span>friends<span style="color: #990000">,</span> <span style="color: #990000">:</span>class_name <span style="color: #990000">=&gt;</span> <span style="color: #FF0000">"User"</span><span style="color: #990000">,</span>

     <span style="color: #990000">:</span>foreign_key <span style="color: #990000">=&gt;</span> <span style="color: #FF0000">"this_user_id"</span><span style="color: #990000">,</span> <span style="color: #990000">:</span>association_foreign_key <span style="color: #990000">=&gt;</span> <span style="color: #FF0000">"other_user_id"</span>

 <span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>

+<h5 id="_tt_autosave_tt_4"><tt>:autosave</tt></h5>

+<div class="paragraph"><p>If you set the <tt>:autosave</tt> option to <tt>true</tt>, Rails will save any loaded members and destroy members that are marked for destruction whenever you save the parent object.</p></div>

 <h5 id="_tt_class_name_tt_4"><tt>:class_name</tt></h5>

 <div class="paragraph"><p>If the name of the other model cannot be derived from the association name, you can use the <tt>:class_name</tt> option to supply the model name. For example, if a part has many assemblies, but the actual name of the model containing assemblies is <tt>Gadget</tt>, you&#8217;d set things up this way:</p></div>

 <div class="listingblock">

@@ -2293,6 +2321,11 @@ http://www.gnu.org/software/src-highlite -->
 <div class="ulist"><ul>

 <li>

 <p>

+February 1, 2009: Added <tt>:autosave</tt> option <a href="../authors.html#mgunderloy">Mike Gunderloy</a>

+</p>

+</li>

+<li>

+<p>

 September 28, 2008: Corrected <tt>has_many :through</tt> diagram, added polymorphic diagram, some reorganization by <a href="../authors.html#mgunderloy">Mike Gunderloy</a> . First release version.

 </p>

 </li>

diff --git a/railties/doc/guides/html/getting_started_with_rails.html b/railties/doc/guides/html/getting_started_with_rails.html
index 564d5c7c00..bd1ce052ac 100644
--- a/railties/doc/guides/html/getting_started_with_rails.html
+++ b/railties/doc/guides/html/getting_started_with_rails.html
@@ -1828,13 +1828,43 @@ Running <tt>rake doc:rails</tt> will put a full copy of the API documentation fo
 <h2 id="_changelog">11. Changelog</h2>

 <div class="sectionbody">

 <div class="paragraph"><p><a href="http://rails.lighthouseapp.com/projects/16213-rails-guides/tickets/2">Lighthouse ticket</a></p></div>

-<div class="paragraph"><p>*

-* November 3, 2008: Formatting patch from Dave Rothlisberger

-* November 1, 2008: First approved version by <a href="../authors.html#mgunderloy">Mike Gunderloy</a>

-* October 16, 2008: Revised based on feedback from Pratik Naik by <a href="../authors.html#mgunderloy">Mike Gunderloy</a> (not yet approved for publication)

-* October 13, 2008: First complete draft by <a href="../authors.html#mgunderloy">Mike Gunderloy</a> (not yet approved for publication)

-* October 12, 2008: More detail, rearrangement, editing by <a href="../authors.html#mgunderloy">Mike Gunderloy</a> (not yet approved for publication)

-* September 8, 2008: initial version by James Miller (not yet approved for publication)</p></div>

+<div class="ulist"><ul>

+<li>

+<p>

+February 1, 2009: Updated for Rails 2.3 by <a href="../authors.html#mgunderloy">Mike Gunderloy</a>

+</p>

+</li>

+<li>

+<p>

+November 3, 2008: Formatting patch from Dave Rothlisberger

+</p>

+</li>

+<li>

+<p>

+November 1, 2008: First approved version by <a href="../authors.html#mgunderloy">Mike Gunderloy</a>

+</p>

+</li>

+<li>

+<p>

+October 16, 2008: Revised based on feedback from Pratik Naik by <a href="../authors.html#mgunderloy">Mike Gunderloy</a> (not yet approved for publication)

+</p>

+</li>

+<li>

+<p>

+October 13, 2008: First complete draft by <a href="../authors.html#mgunderloy">Mike Gunderloy</a> (not yet approved for publication)

+</p>

+</li>

+<li>

+<p>

+October 12, 2008: More detail, rearrangement, editing by <a href="../authors.html#mgunderloy">Mike Gunderloy</a> (not yet approved for publication)

+</p>

+</li>

+<li>

+<p>

+September 8, 2008: initial version by James Miller (not yet approved for publication)

+</p>

+</li>

+</ul></div>

 </div>

 
     </div>