Module | ActiveRecord::Associations::PolymorphicClassMethods |
In: |
lib/has_many_polymorphs/class_methods.rb
|
Class methods added to ActiveRecord::Base for setting up polymorphic associations.
STI association targets must enumerated and named. For example, if Dog and Cat both inherit from Animal, you still need to say [:dogs, :cats], and not [:animals].
Namespaced models follow the Rails underscore convention. ZooAnimal::Lion becomes :’zoo_animal/lion‘.
You do not need to set up any other associations other than for either the regular method or the double. The join associations and all individual and reverse associations are generated for you. However, a join model and table are required.
There is a tentative report that you can make the parent model be its own join model, but this is untested.
This method creates a doubled-sided polymorphic relationship. It must be called on the join model:
class Devouring < ActiveRecord::Base belongs_to :eater, :polymorphic => true belongs_to :eaten, :polymorphic => true acts_as_double_polymorphic_join( :eaters => [:dogs, :cats], :eatens => [:cats, :birds] ) end
The method works by defining one or more special has_many_polymorphs association on every model in the target lists, depending on which side of the association it is on. Double self-references will work.
The two association names and their value arrays are the only required parameters.
These options are passed through to targets on both sides of the association. If you want to affect only one side, prepend the key with the name of that side. For example, :eaters_extend.
:dependent: | Accepts :destroy, :nullify, or :delete_all. Controls how the join record gets treated on any association delete (whether from the polymorph or from an individual collection); defaults to :destroy. |
:skip_duplicates: | If true, will check to avoid pushing already associated records (but also triggering a database load). Defaults to true. |
:rename_individual_collections: | If true, all individual collections are prepended with the polymorph name, and the children‘s parent collection is appended with "_of_#{association_name}". |
:extend: | One or an array of mixed modules and procs, which are applied to the polymorphic association (usually to define custom methods). |
:join_extend: | One or an array of mixed modules and procs, which are applied to the join association. |
:conditions: | An array or string of conditions for the SQL WHERE clause. |
:order: | A string for the SQL ORDER BY clause. |
:limit: | An integer. Affects the polymorphic and individual associations. |
:offset: | An integer. Only affects the polymorphic association. |
:namespace: | A symbol. Prepended to all the models in the :from and :through keys. This is especially useful for Camping, which namespaces models by default. |
This method createds a single-sided polymorphic relationship.
class Petfood < ActiveRecord::Base has_many_polymorphs :eaters, :from => [:dogs, :cats, :birds] end
The only required parameter, aside from the association name, is :from.
The method generates a number of associations aside from the polymorphic one. In this example Petfood also gets dogs, cats, and birds, and Dog, Cat, and Bird get petfoods. (The reverse association to the parents is always plural.)
:from: | An array of symbols representing the target models. Required. |
:as: | A symbol for the parent‘s interface in the join—what the parent ‘acts as’. |
:through: | A symbol representing the class of the join model. Follows Rails defaults if not supplied (the parent and the association names, alphabetized, concatenated with an underscore, and singularized). |
:dependent: | Accepts :destroy, :nullify, :delete_all. Controls how the join record gets treated on any associate delete (whether from the polymorph or from an individual collection); defaults to :destroy. |
:skip_duplicates: | If true, will check to avoid pushing already associated records (but also triggering a database load). Defaults to true. |
:rename_individual_collections: | If true, all individual collections are prepended with the polymorph name, and the children‘s parent collection is appended with "of#{association_name}"</tt>. For example, zoos becomes zoos_of_animals. This is to help avoid method name collisions in crowded classes. |
:extend: | One or an array of mixed modules and procs, which are applied to the polymorphic association (usually to define custom methods). |
:join_extend: | One or an array of mixed modules and procs, which are applied to the join association. |
:parent_extend: | One or an array of mixed modules and procs, which are applied to the target models’ association to the parents. |
:conditions: | An array or string of conditions for the SQL WHERE clause. |
:parent_conditions: | An array or string of conditions which are applied to the target models’ association to the parents. |
:order: | A string for the SQL ORDER BY clause. |
:parent_order: | A string for the SQL ORDER BY which is applied to the target models’ association to the parents. |
:group: | An array or string of conditions for the SQL GROUP BY clause. Affects the polymorphic and individual associations. |
:limit: | An integer. Affects the polymorphic and individual associations. |
:offset: | An integer. Only affects the polymorphic association. |
:namespace: | A symbol. Prepended to all the models in the :from and :through keys. This is especially useful for Camping, which namespaces models by default. |
:uniq: | If true, the records returned are passed through a pure-Ruby uniq before they are returned. Rarely needed. |
:foreign_key: | The column name for the parent‘s id in the join. |
:foreign_type_key: | The column name for the parent‘s class name in the join, if the parent itself is polymorphic. Rarely needed—if you‘re thinking about using this, you almost certainly want to use acts_as_double_polymorphic_join() instead. |
:polymorphic_key: | The column name for the child‘s id in the join. |
:polymorphic_type_key: | The column name for the child‘s class name in the join. |
If you pass a block, it gets converted to a Proc and added to :extend.
When you request an individual association, non-applicable but fully-qualified fields in the polymorphic association‘s :conditions, :order, and :group options get changed to NULL. For example, if you set :conditions => "dogs.name != ‘Spot’", when you request .cats, the conditions string is changed to NULL != ‘Spot‘.
Be aware, however, that NULL != ‘Spot‘ returns false due to SQL‘s 3-value logic. Instead, you need to use the :conditions string "dogs.name IS NULL OR dogs.name != ‘Spot’" to get the behavior you probably expect for negative matches.