ActiveRecord::Associations::ClassMethods (Module)

In: vendor/activerecord/lib/active_record/associations.rb

Associations are a set of macro-like class methods for tying objects together through foreign keys. They express relationships like "Project has one Project Manager" or "Project belongs to a Portfolio". Each macro adds a number of methods to the class which are specialized according to the collection or association symbol and the options hash. It works much the same was as Ruby’s own attr* methods. Example:

  class Project < ActiveRecord::Base
    belongs_to              :portfolio
    has_one                 :project_manager
    has_many                :milestones
    has_and_belongs_to_many :categories
  end

The project class now has the following methods to ease the traversel and manipulation of its relationships:

  • Project#portfolio, Project#portfolio=(portfolio), Project#has_portfolio?, Project#portfolio?(portfolio), Project#build_portfolio, Project#create_portfolio
  • Project#project_manager, Project#project_manager=(project_manager), Project#has_project_manger?, Project#project_manager?(project_manager), Project#build_project_manager, Project#create_project_manager
  • Project#has_milestones?, Project#milestones_count, Project#milestones, Project#milestones<<(milestone), Project#milestones.delete(milestone), Project#find_in_milestones(milestone_id), Project#build_to_milestones, Project#create_in_milestones<
  • Project#has_categories?, Project#categories_count, Project#categories, Project#add_categories(category1, category2), Project#remove_categories(category1, category2), Project#categories<<(category1), Project#categories.delete(category1)

Caching

All of the methods are built on a simple caching principle that will keep the result of the last query around unless specifically instructed not to. The cache is even shared across methods to make it even cheaper to use the macro-added methods without worrying too much about performance at the first go. Example:

  project.milestones             # fetches milestones from the database
  project.milestones_count       # uses the milestone cache
  project.has_milestones?        # uses the milestone cache
  project.milestones_count(true) # fetches milestones from the database
  project.milestones             # uses the milestone cache

Modules

By default, associations will look for objects within the current module scope. Consider:

  module MyApplication
    module Business
      class Firm < ActiveRecord::Base
         has_many :clients
       end

      class Company < ActiveRecord::Base; end
    end
  end

When Firm#clients is called, it’ll in turn call MyApplication::Business::Company.find(firm.id). If you want to associate with a class in another module scope this can be done by specifying the complete class name, such as:

  module MyApplication
    module Business
      class Firm < ActiveRecord::Base; end
    end

    module Billing
      class Account < ActiveRecord::Base
        belongs_to :firm, :class_name => "MyApplication::Business::Firm"
      end
    end
  end

Options

All of the association macros can be specialized through options which makes more complex cases than the simple and guessable ones possible.

Public Instance methods

Adds the following methods for retrival and query of collections of associated objects. collection is replaced with the symbol passed as the first argument, so has_many :clients would add among others has_clients?.

  • collection(force_reload = false) - returns an array of all the associated objects. An empty array is returned if none is found.
  • collection<<(object) - adds the object to the collection (by setting the foreign key on it) and saves it.
  • collection.delete(object) - removes the association by setting the foreign key to null on the associated object.
  • has_collection?(force_reload = false) - returns true if there’s any associated objects.
  • collection_count(force_reload = false) - returns the number of associated objects.
  • find_in_collection(id) - finds an associated object responding to the id and that meets the condition that it has to be associated with this object.
  • build_to_collection(attributes = {}) - returns a new object of the collection type that has been instantiated with attributes and linked to this object through a foreign key but has not yet been saved.
  • create_in_collection(attributes = {}) - returns a new object of the collection type that has been instantiated with attributes and linked to this object through a foreign key and that has already been saved (if it passed the validation).

Example: A Firm class declares has_many :clients, which will add:

  • Firm#clients (similar to Clients.find_all "firm_id = #{id}")
  • Firm#clients<<
  • Firm#clients.delete
  • Firm#has_clients? (similar to firm.clients.length > 0)
  • Firm#clients_count (similar to Client.count "firm_id = #{id}")
  • Firm#find_in_clients (similar to Client.find_on_conditions(id, "firm_id = #{id}")
  • Firm#build_to_clients (similar to Client.new("firm_id" => id))
  • Firm#create_in_clients (similar to c = Client.new("client_id" => id); c.save; c)

The declaration can also include an options hash to specialize the generated methods.

Options are:

  • :class_name - specify the class name of the association. Use it only if that name can’t be infered from the association name. So has_many :products will by default be linked to the Product class, but if the real class name is SpecialProduct, you’ll have to specify it with this option.
  • :conditions - specify the conditions that the associated objects must meet in order to be included as a "WHERE" sql fragment, such as "price > 5 AND name LIKE ‘B%’".
  • :order - specify the order in which the associated objects are returned as a "ORDER BY" sql fragment, such as "last_name, first_name DESC"
  • :foreign_key - specify the foreign key used for the association. By default this is guessed to be the name of this class in lower-case and "_id" suffixed. So a Person class that makes a has_many association will use "person_id" as the default foreign_key.
  • :dependent - if set to true all the associated object are destroyed alongside this object
  • :exclusively_dependent - if set to true all the associated object are deleted in one SQL statement without having their before_destroy callback run. This should only be used on associations that depend solely on this class and don’t need to do any clean-up in before_destroy. The upside is that it’s much faster, especially if there’s a counter_cache involved.
  • :finder_sql - specify a complete SQL statement to fetch the association. This is a good way to go for complex associations that depends on multiple tables. Note: When this option is used, find_in_collection is not added.

Option examples:

  has_many :comments, :order => "posted_on"
  has_many :people, :class_name => "Person", :conditions => "deleted = 0", :order => "name"
  has_many :tracks, :order => "position", :dependent => true
  has_many :subscribers, :class_name => "Person", :finder_sql =>
      'SELECT DISTINCT people.* ' +
      'FROM people p, post_subscriptions ps ' +
      'WHERE ps.post_id = #{id} AND ps.person_id = p.id ' +
      'ORDER BY p.first_name'

[Source]

     # File vendor/activerecord/lib/active_record/associations.rb, line 131
131:       def has_many(collection_id, options = {})
132:         validate_options([ :foreign_key, :class_name, :exclusively_dependent, :dependent, :conditions, :order, :finder_sql ], options.keys)
133: 
134:         collection_name, collection_class_name, class_primary_key_name =
135:             associate_identification(collection_id, options[:class_name], options[:foreign_key])
136: 
137:         if options[:finder_sql]
138:           counter_sql = options[:finder_sql].gsub(/SELECT (.*) FROM/, "SELECT COUNT(*) FROM")
139: 
140:           collection_finder  = "#{collection_class_name}.find_by_sql(\"#{options[:finder_sql]}\")"
141:           collection_counter = "#{collection_class_name}.count_by_sql(\"#{counter_sql}\")"
142:         else
143:           collection_finder = "\#{collection_class_name}.find_all(\n\"\#{class_primary_key_name} = '\\\#{id}'\#{options[:conditions] ? \" AND \" + options[:conditions] : \"\"}\",\n\#{options[:order] ? \"\\\"\" + options[:order] + \"\\\"\" : \"nil\" }\n)\n"
144:           
145:           collection_counter = "#{collection_class_name}.count(\"#{class_primary_key_name} = '\#{id}'\")"
146:         end
147:         
148:         has_collection_method(collection_name)
149:         collection_count_method(collection_name, collection_counter)
150:         collection_accessor_method_for_has_many(collection_name, collection_finder, class_primary_key_name)
151:                                 
152:         build_method("build_to_", collection_name, collection_class_name, class_primary_key_name)
153:         create_method("create_in_", collection_name, collection_class_name, class_primary_key_name)
154: 
155:         # Can't use constrained finds with specialized finder SQL
156:         unless options[:finder_sql]
157:           find_in_collection_method(collection_name, collection_class_name, class_primary_key_name, options[:conditions])
158:         end
159: 
160:         if options[:dependent]
161:           module_eval "before_destroy '#{collection_name}.each { |o| o.destroy }'"
162:         end
163:         
164:         if options[:exclusively_dependent]
165:           module_eval "before_destroy \"#{collection_class_name}.delete_all(%(#{class_primary_key_name} = '\#{id}'))\""
166:         end
167:       end

Adds the following methods for retrival and query of a single associated object. association is replaced with the symbol passed as the first argument, so has_one :manager would add among others has_manager?.

  • association(force_reload = false) - returns the associated object. Nil is returned if none is found.
  • association=(associate) - assigns the associate object, extracts the primary key, sets it as the foreign key, and saves the associate object.
  • association?(object, force_reload = false) - returns true if the object is of the same type and has the same id as the associated object.
  • has_association?(force_reload = false) - returns true if there’s an associated object.
  • build_association(attributes = {}) - returns a new object of the associated type that has been instantiated with attributes and linked to this object through a foreign key but has not yet been saved.
  • create_association(attributes = {}) - returns a new object of the associated type that has been instantiated with attributes and linked to this object through a foreign key and that has already been saved (if it passed the validation).

Example: An Account class declares has_one :beneficiary, which will add:

  • Account#beneficiary (similar to Beneficiary.find_first "account_id = #{id}")
  • Account#beneficiary=(beneficiary) (similar to beneficiary.account_id = account.id; beneficiary.save)
  • Account#beneficiary? (similar to account.beneficiary == some_beneficiary)
  • Account#has_beneficiary? (similar to !account.beneficiary.nil?)
  • Account#build_beneficiary (similar to Beneficiary.new("account_id" => id))
  • Account#create_beneficiary (similar to b = Beneficiary.new("account_id" => id); b.save; b)

The declaration can also include an options hash to specialize the generated methods.

Options are:

  • :class_name - specify the class name of the association. Use it only if that name can’t be infered from the association name. So has_one :manager will by default be linked to the Manager class, but if the real class name is Person, you’ll have to specify it with this option.
  • :conditions - specify the conditions that the associated object must meet in order to be included as a "WHERE" sql fragment, such as "rank = 5".
  • :order - specify the order from which the associated object will be picked at the top. Specified as
     an "ORDER BY" sql fragment, such as "last_name, first_name DESC"
    
  • :dependent - if set to true the associated object is destroyed alongside this object
  • :foreign_key - specify the foreign key used for the association. By default this is guessed to be the name of this class in lower-case and "_id" suffixed. So a Person class that makes a has_one association will use "person_id" as the default foreign_key.

Option examples:

  has_one :credit_card, :dependent => true
  has_one :last_comment, :class_name => "Comment", :order => "posted_on"
  has_one :project_manager, :class_name => "Person", :conditions => "role = 'project_manager'"

[Source]

     # File vendor/activerecord/lib/active_record/associations.rb, line 215
215:       def has_one(association_id, options = {})
216:         options.merge!({ :remote => true })
217:         belongs_to(association_id, options)
218: 
219:         association_name, association_class_name, class_primary_key_name =
220:             associate_identification(association_id, options[:class_name], options[:foreign_key])
221: 
222:         has_one_writer_method(association_name, class_primary_key_name)
223:         build_method("build_", association_name, association_class_name, class_primary_key_name)
224:         create_method("create_", association_name, association_class_name, class_primary_key_name)
225:         
226:         module_eval "before_destroy '#{association_name}.destroy if has_#{association_name}?'" if options[:dependent]
227:       end

Adds the following methods for retrival and query for a single associated object that this object holds an id to. association is replaced with the symbol passed as the first argument, so belongs_to :author would add among others has_author?.

  • association(force_reload = false) - returns the associated object. Nil is returned if none is found.
  • association=(associate) - assigns the associate object, extracts the primary key, and sets it as the foreign key.
  • association?(object, force_reload = false) - returns true if the object is of the same type and has the same id as the associated object.
  • has_association?(force_reload = false) - returns true if there’s an associated object.

Example: An Post class declares has_one :author, which will add:

  • Post#author (similar to Author.find(author_id))
  • Post#author=(author) (similar to post.author_id = author.id)
  • Post#author? (similar to post.author == some_author)
  • Post#has_author? (similar to !post.author.nil?)

The declaration can also include an options hash to specialize the generated methods.

Options are:

  • :class_name - specify the class name of the association. Use it only if that name can’t be infered from the association name. So has_one :author will by default be linked to the Author class, but if the real class name is Person, you’ll have to specify it with this option.
  • :conditions - specify the conditions that the associated object must meet in order to be included as a "WHERE" sql fragment, such as "authorized = 1".
  • :order - specify the order from which the associated object will be picked at the top. Specified as an "ORDER BY" sql fragment, such as "last_name, first_name DESC"
  • :foreign_key - specify the foreign key used for the association. By default this is guessed to be the name of the associated class in lower-case and "_id" suffixed. So a Person class that makes a belongs_to association to a Boss class will use "boss_id" as the default foreign_key.
  • :counter_cache - caches the number of belonging objects on the associate class through use of increment_counter and decrement_counter. The counter cache is incremented when an object of this class is created and decremented when it’s destroyed. This requires that a column named "#{table_name}_count" (such as comments_count for a belonging Comment class) is used on the associate class (such as a Post class).

Option examples:

  belongs_to :firm, :foreign_key => "client_of"
  belongs_to :author, :class_name => "Person", :foreign_key => "author_id"
  belongs_to :valid_coupon, :class_name => "Coupon", :foreign_key => "coupon_id",
             :conditions => 'discounts > #{payments_count}'

[Source]

     # File vendor/activerecord/lib/active_record/associations.rb, line 266
266:       def belongs_to(association_id, options = {})
267:         validate_options([ :class_name, :foreign_key, :remote, :conditions, :order, :dependent, :counter_cache ], options.keys)
268: 
269:         association_name, association_class_name, class_primary_key_name =
270:             associate_identification(association_id, options[:class_name], options[:foreign_key])
271: 
272:         association_class_primary_key_name = options[:foreign_key] || association_class_name.gsub(/^.*::/, '').downcase + "_id"
273: 
274:         if options[:remote]
275:           association_finder = "\#{association_class_name}.find_first(\n\"\#{class_primary_key_name} = '\\\#{id}'\#{options[:conditions] ? \" AND \" + options[:conditions] : \"\"}\",\n\#{options[:order] ? \"\\\"\" + options[:order] + \"\\\"\" : \"nil\" }\n)\n"
276:         else
277:           association_finder = options[:conditions] ?
278:             "#{association_class_name}.find_on_conditions(#{association_class_primary_key_name}, \"#{options[:conditions]}\")" :
279:             "#{association_class_name}.find(#{association_class_primary_key_name})"
280:         end
281: 
282:         has_association_method(association_name)
283:         association_reader_method(association_name, association_finder)
284:         belongs_to_writer_method(association_name, association_class_primary_key_name)
285:         association_comparison_method(association_name, association_class_name)
286: 
287:         if options[:counter_cache]
288:           module_eval(
289:             "after_create '#{association_class_name}.increment_counter(\"#{table_name + "_count"}\", #{association_class_primary_key_name})" +
290:             " if has_#{association_name}?'"
291:           )
292: 
293:           module_eval(
294:             "before_destroy '#{association_class_name}.decrement_counter(\"#{table_name + "_count"}\", #{association_class_primary_key_name})" +
295:             " if has_#{association_name}?'"
296:           )          
297:         end
298:       end

Associates two classes via an intermediate join table. Unless the join table is explicitly specified as an option, it is guessed using the lexical order of the class names. So a join between Developer and Project will give the default join table name of "developers_projects" because "D" outranks "C". Adds the following methods for retrival and query. collection is replaced with the symbol passed as the first argument, so has_and_belongs_to_many :categories would add among others add_categories.

  • collection(force_reload = false) - returns an array of all the associated objects. An empty array is returned if none is found.
  • has_collection?(force_reload = false) - returns true if there’s any associated objects.
  • collection_count(force_reload = false) - returns the number of associated objects.
  • add_collection(object1, object2) - adds an association between this object and the objects given as arguments. The object arguments can either be given one by one or in an array.
  • collection<<(object) - adds an association between this object and the object given as argument. Multiple associations can be created by passing an array of objects instead.
  • remove_collection(object1, object2) - removes the association between this object and the objects given as arguments. The object arguments can either be given one by one or in an array.
  • collection.delete(object) - removes the association between this object and the object given as argument. Multiple associations can be removed by passing an array of objects instead.

Example: An Developer class declares has_and_belongs_to_many :projects, which will add:

  • Developer#projects
  • Developer#has_projects?
  • Developer#projects_count
  • Developer#add_projects
  • Developer#projects<<
  • Developer#remove_projects
  • Developer#projects.delete

The declaration can also include an options hash to specialize the generated methods.

Options are:

  • :class_name - specify the class name of the association. Use it only if that name can’t be infered from the association name. So has_and_belongs_to_many :projects will by default be linked to the Project class, but if the real class name is SuperProject, you’ll have to specify it with this option.
  • :join_table - specify the name of the join table if the default based on lexical order isn’t what you want
  • :foreign_key - specify the foreign key used for the association. By default this is guessed to be the name of this class in lower-case and "_id" suffixed. So a Person class that makes a has_and_belongs_to_many association will use "person_id" as the default foreign_key.
  • :association_foreign_key - specify the association foreign key used for the association. By default this is guessed to be the name of the associated class in lower-case and "_id" suffixed. So the associated class is Project that makes a has_and_belongs_to_many association will use "project_id" as the default association foreign_key.
  • :finder_sql - overwrite the default generated SQL used to fetch the association with a manual one
  • :delete_sql - overwrite the default generated SQL used to remove links between the associated classes with a manual one
  • :insert_sql - overwrite the default generated SQL used to add links between the associated classes with a manual one

Option examples:

  has_and_belongs_to_many :projects
  has_and_belongs_to_many :nations, :class_name => "Country"
  has_and_belongs_to_many :categories, :join_table => "prods_cats"

[Source]

     # File vendor/activerecord/lib/active_record/associations.rb, line 356
356:       def has_and_belongs_to_many(association_id, options = {})
357:         validate_options([ :class_name, :table_name, :foreign_key, :association_foreign_key,
358:                            :join_table, :finder_sql, :delete_sql, :insert_sql ], options.keys)
359: 
360:         association_name, association_class_name, association_class_primary_key_name =
361:             associate_identification(association_id, options[:class_name], options[:foreign_key])
362: 
363: 
364:         association_foreign_key = options[:association_foreign_key] || association_class_name.downcase + "_id"
365: 
366:         association_table_name = options[:table_name] || table_name(association_class_name)
367:         join_table  = options[:join_table] || 
368:           join_table_name(undecorated_table_name(self.to_s), undecorated_table_name(association_class_name))
369: 
370:         finder_sql  = 
371:           options[:finder_sql] ||
372:           "SELECT t.* FROM #{association_table_name} t, #{join_table} j " +
373:           "WHERE t.\#{self.class.primary_key} = j.#{association_foreign_key} AND j.#{association_class_primary_key_name} = '\#{id}' ORDER BY t.\#{self.class.primary_key}"
374: 
375:         has_collection_method(association_name)
376:         collection_accessor_method_for_has_and_belongs_to_many(association_name, "#{association_class_name}.find_by_sql(\"#{finder_sql}\")")
377:         collection_count_method(association_name, "#{association_name}.length")
378: 
379:         add_association_relation(
380:           association_name, 
381:           options[:insert_sql] || 
382:             "INSERT INTO #{join_table} (#{association_class_primary_key_name}, #{association_foreign_key}) " +
383:             "VALUES ('\#{id}', '\#{item.id}')"
384:         )
385: 
386:         remove_association_relation(
387:           association_name, association_foreign_key, 
388:           options[:delete_sql] || "DELETE FROM #{join_table} WHERE #{association_class_primary_key_name} = '\#{id}'"
389:         )
390:       end

[Validate]