A failing test which shows that when a collection association is accessed before saving the owner, the proxy caches the #bind_values without the owner's id.

[Empact]

This causes calls like: owner.association.update_all to behave unexpectedly
in this case, because they try to act on association objects where
owner_id is null.

This is related to #bind_values being set on first access at:
https://github.com/rails/rails/blob/master/activerecord/lib/active_record/associations/collection_proxy.rb#L37

Not sure how to properly deal with this, but it is the case that calling update all on
the #scope of the association works.

[Empact]

/cc @jonleighton

[Empact]

Hey @carlosantoniodasilva, this is a Rails 4 regression, with more evidence here: https://gist.github.com/Empact/5865555

The output for the above is:

Active Record 3.2.13
-- create_table(:firms, {:force=>true})
   -> 0.1371s
-- create_table(:clients, {:force=>true})
   -> 0.0005s
1 clients. 1 expected.
1 clients updated. 1 expected.

Active Record 4.0.0
-- create_table(:firms, {:force=>true})
   -> 0.1606s
-- create_table(:clients, {:force=>true})
   -> 0.0004s
1 clients. 1 expected.
0 clients updated. 1 expected.

Should I re-open this request on 4-0-stable?

[steveklabnik]

All pull requests should be opened against master, they'll be backported appropriately.

That said let's see if @carlosantoniodasilva agrees this is actually a bug.

[Empact]

Hit this again in tests, reopened against master as #11694