| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
favour of defining a 'default_scope' class method in the model. See the CHANGELOG for more details.
|
|
|
|
| |
There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?.
|
|
|
|
| |
Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
|
|
|
|
|
|
| |
This reverts commit 45c233ef819dc7b67e259dd73f24721fec28b8c8.
Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
|
|
|
|
| |
Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
|
| |
|
| |
|
|
|
|
| |
not in ON constraints because postgres requires that the table has been joined before the condition references it.
|
|
|
|
| |
the code which support this
|
|
|
|
| |
instantiate one AR object per actual record in the database. (Even when IM is off.)
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
activerecord/CHANGELOG
activerecord/lib/active_record/association_preload.rb
activerecord/lib/active_record/associations.rb
activerecord/lib/active_record/associations/class_methods/join_dependency.rb
activerecord/lib/active_record/associations/class_methods/join_dependency/join_association.rb
activerecord/lib/active_record/associations/has_many_association.rb
activerecord/lib/active_record/associations/has_many_through_association.rb
activerecord/lib/active_record/associations/has_one_association.rb
activerecord/lib/active_record/associations/has_one_through_association.rb
activerecord/lib/active_record/associations/through_association_scope.rb
activerecord/lib/active_record/reflection.rb
activerecord/test/cases/associations/has_many_through_associations_test.rb
activerecord/test/cases/associations/has_one_through_associations_test.rb
activerecord/test/cases/reflection_test.rb
activerecord/test/cases/relations_test.rb
activerecord/test/fixtures/memberships.yml
activerecord/test/models/categorization.rb
activerecord/test/models/category.rb
activerecord/test/models/member.rb
activerecord/test/models/reference.rb
activerecord/test/models/tagging.rb
|
| | |
|
| |
| |
| |
| | |
callbacks etc) rather than calling a whole bunch of methods with rather long names.
|
| | |
|
| |
| |
| |
| | |
1644663ba7f678d178deab2bf1629dc05626f85b
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
activerecord/lib/active_record/associations/association.rb
activerecord/lib/active_record/fixtures.rb
|
| | |
| | |
| | |
| | | |
manages the association, and a CollectionProxy class which is *only* a proxy. Singular associations no longer have a proxy. See CHANGELOG for more.
|
| | |
| | |
| | |
| | | |
the join record is automatically saved too. This requires the :inverse_of option to be set on the source association in the join model. See the CHANGELOG for details. [#4329 state:resolved]
|
| | |
| | |
| | |
| | | |
is a has_many :through with a :primary_key option on the source reflection. [#6376 state:resolved]
|
| | | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
activerecord/examples/performance.rb
activerecord/lib/active_record/association_preload.rb
activerecord/lib/active_record/associations.rb
activerecord/lib/active_record/associations/association_proxy.rb
activerecord/lib/active_record/autosave_association.rb
activerecord/lib/active_record/base.rb
activerecord/lib/active_record/nested_attributes.rb
activerecord/test/cases/relations_test.rb
|
| | |
| | |
| | |
| | | |
... } rather than instance_eval-ing strings
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
[#6423 state:committed]
Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
|
| | | |
|
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | | |
records in the join table. This is to make the destroy method more consistent across the different types of associations. For more details see the CHANGELOG entry.
|
| | | |
|
| | |
| | |
| | |
| | | |
log the same things
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
|
| | |
| | |
| | |
| | | |
hash for the through record, because the creation is done directly on the through association, which will already handle setting the conditions.
|
| | |
| | |
| | |
| | | |
should return self.
|
| | |
| | |
| | |
| | | |
#replace which was previously incorrect, but the test passed due to the fact that to_a was not duping.
|
| | | |
|
| | |
| | |
| | |
| | | |
this can affect validations/callbacks/etc inside the record itself [#6252 state:resolved]
|
| | |
| | |
| | |
| | | |
table. This has been documented as deprecated behaviour since April 2006. Please use has_many :through instead. A deprecation warning will be added to the 3-0-stable branch for the 3.0.4 release.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
[#6257 state:resolved]
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
the code that need that can now just use association_proxy(:name).loaded?/target=
|
| | |
| | |
| | |
| | | |
replaced
|