Add test to specify that attributes from an association's conditions should be assigned without mass-assignment protection when a record is built on the association.

singular and collection relations in AR can now specify mass-assignment security options (:as and :without_protection) in build, create and create! methods.

Signed-off-by: NSantiago Pastorino and José Ignacio Costa <santiago+jose@wyeworks.com>

Correctly update counter caches on deletion for has_many :through [#2824 state:resolved]. Also fixed a bunch of other counter cache bugs in the process, as once I fixed this one others started appearing like nobody's business.

Support the :dependent option on has_many :through associations. For historical and practical reasons, :delete_all is the default deletion strategy employed by association.delete(*records), despite the fact that the default strategy is :nullify for regular has_many. Also, this only works at all if the source reflection is a belongs_to. For other situations, you should directly modify the through association.

Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Fix creation of has_many through records with custom primary_key option on belongs_to [#2990 state:resolved]

has_many associations with :dependent => :delete_all should update the counter cache when deleting records

Verify that creating a has_many through record where there is a default_scope on the join model works correctly (creates the join record with the default scope applied)

Verify that creating a has_many through record where there is a default_scope on the join model works correctly (creates the join record with the default scope applied)

made a pass in AR's schema.rb to keep (most) create statements in lexicographic order, and fixed an FK

This way parent models can get their own after_create and
after_update callbacks fired after has_one has done its job.

Support for :primary_key option on the source reflection of a through association, where the source is a has_one or has_many

Add support for nested through associations in JoinAssociation. Hence Foo.joins(:bar) will work for through associations. There is some duplicated code now, which will be refactored.

Signed-off-by: NMichael Koziarski <michael@koziarski.com>

While creating a new record using has_many create method default scope of child should be respected.

author.posts.create should take into account default_scope
defined on post.

[#3939: state:resolved]
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

Signed-off-by: NJosé Valim <jose.valim@gmail.com>

Signed-off-by: NJosé Valim <jose.valim@gmail.com>

[#4971 state:resolved]
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

Signed-off-by: NJosé Valim <jose.valim@gmail.com>

[#5106 state:resolved]
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

[#5161 state:resolved]

[#5152 state:reslved]

Signed-off-by: NJosé Valim <jose.valim@gmail.com>