Skip to content

Instantly share code, notes, and snippets.

@dreamingblackcat

dreamingblackcat/active_record_objects_autosave.md

Forked from demisx/active_record_objects_autosave.md
Created July 7, 2021 03:38
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save dreamingblackcat/1a8c48b9a8107db0759aa1bf85259263 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save dreamingblackcat/1a8c48b9a8107db0759aa1bf85259263 to your computer and use it in GitHub Desktop.
Download ZIP
When Active Record Child Objects are Autosaved in Rails
Raw
gistfile1.md

belongs_to:

  1. Assigning an object to a belongs_to association does not automatically save the object. It does not save the associated object either.

has_one:

  1. When you assign an object to a has_one association, that object is automatically saved (in order to update its foreign key).
  2. In addition, any object being replaced is also automatically saved, because its foreign key will change too
  3. If either of these saves fails due to validation errors, then the assignment statement returns false and the assignment itself is cancelled.
  4. If the parent object (the one declaring the has_one association) is unsaved (that is, new_record? returns true) then the child objects are not saved. They will automatically when the parent object is saved.
  5. If you want to assign an object to a has_one association without saving the object, use the association.build method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment