ActiveRecord Associations Basics

Direct Answer

Active Record associations declare relationships between model classes and provide methods for navigating and changing related records. In a one-to-many relationship, Post has_many :comments and Comment belongs_to :post; the foreign key normally lives on the belonging table as comments.post_id. The Ruby declarations do not replace database design: migrations should add the reference, index, null rule, and foreign key needed for integrity, and destructive dependency behaviour such as dependent: :destroy must be chosen explicitly.

Deep Dive & Architecture

An association method starts from key metadata. comment.post uses the comment's post_id to find the matching post primary key. post.comments builds the inverse condition. The returned collection is an association relation, so it can often be filtered or ordered before loading.

Building through an association sets linkage in memory. post.comments.build assigns the post relationship to the new comment; persistence still runs the comment's validation and write lifecycle. Creating the child does not automatically make a multi-record operation atomic, so transactions matter when several writes must succeed together.

Database foreign keys protect references even when SQL, background jobs, or another service writes outside the Rails model. An index on the foreign-key column supports the lookup direction. Model-level presence rules improve feedback but cannot replace those database guarantees.

Dependency options encode ownership. If comments have no meaning without their post, destroying them may be correct. If records must remain for audit, cascade deletion may be destructive. Model behaviour and database ON DELETE actions must be designed together so they do not contradict or unexpectedly duplicate work.

Code Example

class Post < ApplicationRecord
  has_many :comments, dependent: :destroy
end

class Comment < ApplicationRecord
  belongs_to :post
end

class AddPostToComments < ActiveRecord::Migration[8.1]
  def change
    add_reference :comments, :post,
                  null: false, index: true, foreign_key: true
  end
end

post = Post.new
comment = post.comments.build(body: "Clear explanation")
puts comment.post.equal?(post)

Common Mistakes & Pitfalls

Forgetting the foreign key convention (post_id) or confusing which side has belongs_to vs has_many.