diff options
| author | Chris Thompson <chris@goclio.com> | 2013-03-07 14:43:00 -0700 |
|---|---|---|
| committer | Aaron Patterson <aaron.patterson@gmail.com> | 2013-04-30 16:14:16 -0700 |
| commit | ebd7cc6f459e43aa03a6b8095266888909e0ee4d (patch) | |
| tree | c64724fa000fc8a911236685650a4834270a187a /ci | |
| parent | e8e2f010afc29669e20b3f2461e1595b122220b8 (diff) | |
| download | rails-ebd7cc6f459e43aa03a6b8095266888909e0ee4d.tar.gz rails-ebd7cc6f459e43aa03a6b8095266888909e0ee4d.tar.bz2 rails-ebd7cc6f459e43aa03a6b8095266888909e0ee4d.zip | |
Fix #8856 Ensure has_one association=(associate) triggers save.
activerecord/lib/active_record/associations.rb states:
# [association=(associate)]
# Assigns the associate object, extracts the primary key, sets it as the foreign key,
# and saves the associate object.
Since commit 42dd5d9f2976677a4bf22347f2dde1a8135dfbb4 to fix #7191, this
is no longer the case if the associate has changed, but is the same
object. For example:
# Pirate has_one :ship
pirate = Pirate.create!(catchphrase: "A Pirate")
ship = pirate.build_ship(name: 'old name')
ship.save!
ship.name = 'new name'
pirate.ship = ship
That last line should trigger a save. Although we are not changing the
association, the associate (ship) has changed.
Diffstat (limited to 'ci')
0 files changed, 0 insertions, 0 deletions