Many to Many associations in Rails HABTM and has_many :through

By -
We've noticed there's a bit of confusion about the differences between the two ways to create many-to-many relationships using Rails associations. 

Has and Belongs to many (HABTM) or Join Table Associations

create_table "dancers_movies", :id => false do |t|
  t.column "dancer_id", :integer, :null => false
  t.column "movie_id",  :integer, :null => false
end

class Dancer < ActiveRecord::Base
  has_and_belongs_to_many :movies
end

class Movie < ActiveRecord::Base
  has_and_belongs_to_many :dancers
end
 

has_and_belongs_to_many associations are simple to set up. The join table has only foreign keys for the models being joined - no primary key or other attributes.There is no model class for the join table.



has many : through or Join Model associations 




create_table "appearances", do |t|
  t.column "dancer_id",      :integer, :null => false
  t.column "movie_id",       :integer, :null => false
  t.column "character_name", :string
  t.column "dance_numbers",  :integer
end




class Appearance < ActiveRecord::Base
  belongs_to :dancer
  belongs_to :movie
end

class Dancer < ActiveRecord::Base
  has_many :appearances, :dependent => true
  has_many :movies, :through => :appearances
end

class Movie < ActiveRecord::Base
  has_many :appearances, :dependent => true
  has_many :dancers, :through => :appearances
end


 



has_many :through associations are pretty easy to set up for the simple case, but can get tricky when using other features like polymorphism. The table for the join model has a primary key and can contain attributes just like any other model.



Conclusion





has_and_belongs_to_many uses a simple join table where 
each row is just two foreign keys. There's no model class for the join 
as the join table records are never accessed directly.



has_many :through upgrades the join table to a full-fledged model. It uses a model class to represent entries in the table.





































Comments











Post a Comment






























Popular posts from this blog









Inserting and Moving elements inside Ruby Array







By







-















Here's is an array with 5 elements  2.1.2 :001 > arr = ["a", "b", "c", "d", "e"]  => ["a", "b", "c", "d", "e"]  Lets look at few different cases  Insert a new element at starting position  Using unshift 2.1.2 :002 > arr.unshift("f")  => ["f", "a", "b", "c", "d", "e"]  Using insert 2.1.2 :005 > arr.insert(0, "f")  => ["f", "a", "b", "c", "d", "e"] In the above example 0 is the position(index)  Move existing element from one position to another   The element in this case is "e"  Using uniq to show only unique elements  2.1.2 :009 > arr.insert(0, "e").uniq  => ["e", "a", "b", "c", "d"]  With uniq we are only showing unique records but the element is listed 








Read more










Difference between Validations, Callbacks and Observers







By







-















 Validations allow you to ensure that only valid data is stored in your  database.   Example:    validates_presence_of :user_name, :password   validates_numericality_of :value   We can write custom validation also as   def validate    errors.add(:price, “should be a positive value”) if price.nil?|| price < 0.01  end    Callbacks and observers allow you to trigger logic before or  after an alteration of an object’s state.   Callbacks  are methods that get called at certain moments of an  object’s  life cycle. With callbacks it’s possible to write code that  will run  whenever an Active Record object is created, saved, updated,  deleted,  validated, or loaded from the database.   Callbacks are hooks into the life cycle of an Active Record object that  allow you to trigger logic before or after an alteration of the object  state. This can be used to make sure that associated and dependent  objects are deleted when destroy is called (by overwriting  before_destroy) or to massage attribu








Read more