This project is archived and is in readonly mode.

#2214 ✓resolved
Jacob Burkhart

Explicit autosave => false should override new_record autosaving

Reported by Jacob Burkhart | March 11th, 2009 @ 04:25 PM | in 2.3.6

previously mentioned in #2144

"autosave" as a feature in rails 2.3 provides the ability to configure a particular model to automatically save the other end of a particular relationship on save.

This behavior existed in earlier version of rails, and would be triggered automatically when a model was saved and it had a relationship to another which was a "new_record?"

Since autosave => true is now a way to make this saving happen for cases beyond new_record:

Here is a patch which makes autosave => false a way to make autosave never happen, including skipping saving of "new_record?" associations.

Comments and changes to this ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>

Attachments

Referenced by

Pages