aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/active_record/associations.rb
Commit message (Collapse)AuthorAgeFilesLines
* Move JoinDependency and friends from ↵Jon Leighton2011-02-281-2/+2
| | | | ActiveRecord::Associations::ClassMethods to just ActiveRecord::Associations
* Rewrote AssociationPreload.Jon Leighton2011-02-281-0/+2
|
* Use proper objects to do the work to build the associations (adding methods, ↵Jon Leighton2011-02-211-387/+22
| | | | callbacks etc) rather than calling a whole bunch of methods with rather long names.
* merges docrailsXavier Noria2011-02-181-1/+1
|\
| * Fix Typos: remove several occurences of the theNicholas Rowe2011-02-171-1/+1
| |
* | Split AssociationProxy into an Association class (and subclasses) which ↵Jon Leighton2011-02-181-34/+30
| | | | | | | | manages the association, and a CollectionProxy class which is *only* a proxy. Singular associations no longer have a proxy. See CHANGELOG for more.
* | Allow building and then later saving has_many :through records, such that ↵Jon Leighton2011-02-181-7/+31
| | | | | | | | 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]
* | Ensure that association_ids uses the correct attribute where the association ↵Jon Leighton2011-02-181-2/+5
| | | | | | | | is a has_many :through with a :primary_key option on the source reflection. [#6376 state:resolved]
* | Documentation for recent refinements to association deletionJon Leighton2011-02-071-3/+75
| |
* | Support the :dependent option on has_many :through associations. For ↵Jon Leighton2011-02-071-2/+1
|/ | | | 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.
* Merge branch 'master' of git://github.com/lifo/docrailsXavier Noria2011-02-051-1/+1
|\
| * keep options titles consistent to "Options"Gabriel Horner2011-02-031-1/+1
| |
* | Fixing ordering of HABTM association deletion [#6191 state:resolved]Edward Faulkner2011-02-041-1/+1
|/ | | | Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
* Removed support for accessing attributes on a has_and_belongs_to_many join ↵Jon Leighton2011-01-161-6/+0
| | | | 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.
* Abstract common code from BelongsToAssociation and HasOneAssociation into ↵Jon Leighton2011-01-161-0/+1
| | | | SingularAssociation
* Document the new create_association! method on one-to-one associationsJon Leighton2011-01-161-1/+9
|
* Add create_association! for belongs_toJon Leighton2011-01-161-3/+3
|
* Support for create_association! for has_one associationsJon Leighton2011-01-111-0/+1
|
* Refactor the code for singular association constructors. This will allow me ↵Jon Leighton2011-01-111-8/+13
| | | | to define a create_association! method in a minute.
* It's not necessary to pass the association proxy class around nowJon Leighton2011-01-111-22/+15
|
* Get rid of set_association_target and association_loaded? as the parts of ↵Jon Leighton2011-01-111-12/+0
| | | | the code that need that can now just use association_proxy(:name).loaded?/target=
* DRY up the code which instantiates the association proxyJon Leighton2011-01-111-35/+24
|
* Document the recent changes to association assignmentJon Leighton2011-01-111-4/+9
|
* Return value is irrelevant here as the RHS of the assignment is always ↵Jon Leighton2011-01-111-1/+0
| | | | returned by methods ending in '='
* Remove incorrect documentation about build_assoc on has_one. This is proven, ↵Jon Leighton2011-01-111-2/+1
| | | | for example, by test_successful_build_association in has_one_associations_test.rb
* For a singular association, it should be build_association, rather than ↵Jon Leighton2011-01-111-1/+1
| | | | association.build (as association may be nil)
* Correctly indent the bullet points under 'One-to-one associations', so that ↵Jon Leighton2011-01-111-10/+10
| | | | the lines are not broken in the generated rdoc html
* Not really worth having the HasAssociation module for just a single methodJon Leighton2011-01-071-1/+0
|
* just use a hash for doing association cachingAaron Patterson2011-01-071-7/+7
|
* no need for selfAaron Patterson2011-01-061-1/+1
|
* Remove undocumented feature from has_one where you could pass false as the ↵Jon Leighton2011-01-031-8/+3
| | | | | | | | | | | | second parameter to build_assoc or create_assoc, and the existing associated object would be untouched (the foreign key would not be nullified, and it would not be deleted). If you want behaviour similar to this you can do the following things: * Use :dependent => :nullify (or don't specify :dependent) if you want to prevent the existing associated object from being deleted * Use has_many if you actually want multiple associated objects * Explicitly set the foreign key if, for some reason, you really need to have multiple objects associated with the same has_one. E.g. previous = obj.assoc obj.create_assoc previous.update_attributes(:obj_id => obj.id)
* When preloading a belongs_to, the target should still be set (to nil) if ↵Jon Leighton2011-01-031-0/+1
| | | | there is no foreign key present. And the loaded flag should be set on the association proxy. This then allows us to remove the foreign_key_present? check from BelongsToAssociation#find_target. Also added a test for the same thing on polymorphic associations.
* Allow assignment on has_one :through where the owner is a new record [#5137 ↵Jon Leighton2011-01-031-11/+12
| | | | | | | | | | state:resolved] This required changing the code to keep the association proxy for a belongs_to around, despite its target being nil. Which in turn required various changes to the way that stale target checking is handled, in order to support various edge cases (loaded target is nil then foreign key added, foreign key is changed and then changed back, etc). A side effect is that the code is nicer and more succinct. Note that I am removing test_no_unexpected_aliasing since that is basically checking that the proxy for a belongs_to *does* change, which is the exact opposite of the intention of this commit. Also adding various tests for various edge cases and related things. Phew, long commit message!
* Have a proper AssociationReflection#foreign_type method rather than using ↵Jon Leighton2011-01-031-7/+1
| | | | options[:foreign_type]
* Add documentation for the :foreign_type option on belongs_toJon Leighton2011-01-031-0/+5
|
* Rename AssociationReflection#primary_key_name to foreign_key, since the ↵Jon Leighton2010-12-311-2/+2
| | | | options key which it relates to is :foreign_key
* Get rid of extra_conditions param from configure_dependency_for_has_many. I ↵Jon Leighton2010-12-311-9/+3
| | | | can't see a particularly plausible argument for this being used by plugins, and if they really want they can just redefine the callback or whatever. Note also that before my recent commit the extra_conditions param was completely ignored for :dependent => :destroy.
* Refactor configure_dependency_for_has_many to use ↵Jon Leighton2010-12-311-38/+20
| | | | AssociationCollection#delete_all. It was necessary to change test_before_destroy in lifecycle_test.rb so that it checks topic.replies.size *before* doing the destroy, as afterwards it will now (correctly) be 0.
* Add a HasAssociation module for common code for has_* associationsJon Leighton2010-12-261-0/+2
|
* Raise an error for associations which try to go :through a polymorphic ↵Jon Leighton2010-12-231-1/+7
| | | | association [#6212 state:resolved]
* If a has_many goes :through a belongs_to, and the foreign key of the ↵Jon Leighton2010-12-231-1/+5
| | | | belongs_to changes, then the has_many should be considered stale.
* Improved strategy for updating a belongs_to association when the foreign key ↵Jon Leighton2010-12-231-42/+1
| | | | changes. Rather than resetting each affected association when the foreign key changes, we should lazily check for 'staleness' (where fk does not match target id) when the association is accessed.
* Revert "Optimize <association>_ids for hm:t with belongs_to source". The ↵Jon Leighton2010-12-231-8/+1
| | | | | | | | | | optimisation has too many edge cases, such as when the reflection, source reflection, or through reflection has conditions, orders, etc. [#6153 state:resolved] This reverts commit 373b053dc8b99dac1abc3879a17a2bf8c30302b5. Conflicts: activerecord/lib/active_record/associations.rb
* Don't allow a has_one association to go :through a collection association ↵Jon Leighton2010-12-231-0/+6
| | | | [#2976 state:resolved]
* removing method to prevent warningsAaron Patterson2010-12-081-0/+4
|
* Setting the id of a belongs_to object updates all referenced objects [#2989 ↵Jeff Dean2010-12-081-0/+37
| | | | state:resolved]
* breaking classes up in to respective filesAaron Patterson2010-11-231-574/+1
|
* class inheritable attributes is used no more! all internal use of class ↵Josh Kalderimis2010-11-201-6/+7
| | | | | | inheritable has been changed to class_attribute. class inheritable attributes has been deprecated. Signed-off-by: José Valim <jose.valim@gmail.com>
* use persisted? instead of new_record? wherever possibleDavid Chelimsky2010-11-091-1/+1
| | | | | | | | | | | - persisted? is the API defined in ActiveModel - makes it easier for extension libraries to conform to ActiveModel APIs without concern for whether the extended object is specifically ActiveRecord [#5927 state:committed] Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
* reduce duplication in assiciations #construct()Aaron Patterson2010-11-061-9/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 19:12:24 +0000