belongs_to relationship in Ruby on Rails - Step-by-Step Execution

Concept Flow - belongs_to relationship

Define belongs_to in Child Model

↓

Child has foreign key pointing to Parent

↓

Create Child instance with Parent assigned

↓

Access Parent from Child via belongs_to

↓

Use Parent data in Child context

This flow shows how a child model declares a belongs_to link to a parent model, stores the parent's id, and accesses the parent through this link.

Execution Sample

Ruby on Rails

class Comment < ApplicationRecord
  belongs_to :post
end

post = Post.create(title: 'Hello World')
comment = Comment.new(post: post)
comment.post.title

Defines a Comment linked to a Post, creates a post with a title, creates a comment with a post, then accesses the post's title from the comment.

Execution Table

Step	Action	State Change	Result
1	Define Comment model with belongs_to :post	Comment model now expects post_id foreign key	Child model linked to Parent
2	Create Post instance with title 'Hello World'	Post object created with id=1	Post saved with id=1
3	Create Comment with post: post	Comment object created with post_id=1	Comment linked to Post with id=1
4	Access comment.post.title	Rails fetches Post with id=1	Returns 'Hello World'
5	End of example	No further state changes	Execution stops

💡 All steps completed, comment successfully linked to post and accessed

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
post	nil	Post(id=1, title='Hello World')	Post(id=1, title='Hello World')	Post(id=1, title='Hello World')	Post(id=1, title='Hello World')
comment	nil	nil	Comment(post_id=1)	Comment(post_id=1)	Comment(post_id=1)

Key Moments - 2 Insights

Why do we need a foreign key like post_id in the Comment model?

The foreign key post_id stores which Post the Comment belongs to. Without it, Rails cannot link the Comment to its Post. See execution_table step 3 where comment gets post_id=1.

How does comment.post.title return the post's title?

belongs_to tells Rails to look up the Post with id=post_id when calling comment.post. Then it accesses the title attribute. See execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of comment.post_id after step 3?

A 1

B nil

C 0

D post

💡 Hint

Check the 'State Change' column in step 3 where comment is created with post_id=1.

At which step does Rails fetch the Post record from the database?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Action' and 'Result' columns in step 4 where comment.post.title is accessed.

If the belongs_to line is removed from Comment, what happens when calling comment.post.title?

A Returns the post title anyway

B Raises an error because comment.post is undefined

C Returns nil silently

D Creates a new Post automatically

💡 Hint

belongs_to defines the method comment.post. Without it, the method does not exist.

Concept Snapshot

belongs_to relationship in Rails:
- Declared in child model (e.g., belongs_to :post)
- Child stores foreign key (post_id) linking to parent
- Access parent via child.parent_method (comment.post)
- Rails fetches parent record automatically
- Enables easy navigation from child to parent

Full Transcript

In Rails, the belongs_to relationship connects a child model to a parent model by storing the parent's id in the child. The child model declares belongs_to :parent_name, which tells Rails to expect a foreign key column like parent_name_id. When you create a child instance and assign a parent, Rails saves the parent's id in the child. Later, accessing child.parent_name calls Rails to fetch the parent record using that id. This lets you easily get parent data from the child. For example, a Comment belongs_to a Post. The comment stores post_id. When you call comment.post.title, Rails fetches the Post with that id and returns its title. Without belongs_to, the child cannot link to the parent or access it this way.

Practice

1. What does the belongs_to association in Rails indicate about the relationship between two models?

easy

A. It creates a many-to-many relationship between two models.

B. The model with belongs_to is the parent and links to many child models.

C. It automatically creates a database table for the association.

D. The model with belongs_to is the child and links to one parent model.

Solution

1. Step 1: Understand the role of belongs_to

   The belongs_to association is used in the child model to link it to a single parent model.

2. Step 2: Identify the relationship direction

   This means the child model holds the foreign key and points to one parent, not many.

3. Final Answer:

   The model with belongs_to is the child and links to one parent model. -> Option D

4. Quick Check:

   belongs_to = child to one parent [OK]

Hint: Remember: belongs_to means child points to one parent [OK]

Common Mistakes:

• Confusing belongs_to with has_many
• Thinking belongs_to creates many-to-many
• Assuming belongs_to creates a new table

2. Which of the following is the correct syntax to declare a belongs_to association in a Rails model named Comment that belongs to a Post?

easy

A. belongs_to :post

B. belongs_to Post

C. has_many :post

D. belongs_to 'post'

Solution

1. Step 1: Recall Rails association syntax

   In Rails, associations use symbols for model names, so belongs_to :post is correct.

2. Step 2: Check other options for syntax errors

   belongs_to Post lacks symbol, has_many is wrong association, and quotes are not standard here.

3. Final Answer:

   belongs_to :post -> Option A

4. Quick Check:

   Use symbol for model name in belongs_to [OK]

Hint: Use symbol (colon) for model name in belongs_to [OK]

Common Mistakes:

• Using class name without colon
• Using has_many instead of belongs_to
• Using string instead of symbol

3. Given the following Rails models:

class Comment < ApplicationRecord
  belongs_to :post
end

class Post < ApplicationRecord
  has_many :comments
end

What will comment.post return if comment is a Comment instance linked to a Post with title "Hello"?

medium

A. The Post object with title "Hello"

B. An array of comments

C. A string "Hello"

D. nil

Solution

1. Step 1: Understand belongs_to usage

   The belongs_to :post means each comment has one post object accessible via comment.post.

2. Step 2: Identify what comment.post returns

   It returns the Post instance linked to that comment, which has the title "Hello".

3. Final Answer:

   The Post object with title "Hello" -> Option A

4. Quick Check:

   comment.post returns parent Post object [OK]

Hint: belongs_to returns the single parent object [OK]

Common Mistakes:

• Expecting an array instead of single object
• Expecting a string instead of object
• Assuming nil when association exists

4. You have this model code:

class Order < ApplicationRecord
  belongs_to :customer
end

When running order.customer, you get an error: undefined method 'customer'. What is the most likely cause?

medium

A. The Customer model is not defined.

B. The belongs_to should be has_many.

C. The customer_id column is missing in the orders table.

D. The association name should be plural: belongs_to :customers.

Solution

1. Step 1: Check database foreign key presence

   The belongs_to :customer requires a customer_id column in the orders table to work.

2. Step 2: Understand error cause

   If customer_id is missing, Rails cannot create the method customer, causing the error.

3. Final Answer:

   The customer_id column is missing in the orders table. -> Option C

4. Quick Check:

   Missing foreign key column causes undefined method error [OK]

Hint: Check foreign key column exists for belongs_to [OK]

Common Mistakes:

• Confusing belongs_to with has_many
• Assuming association name should be plural
• Ignoring missing database column

5. You want to create a Rails app where each Review belongs to a Product, and each product can have many reviews. You also want to ensure deleting a product deletes its reviews automatically. Which setup is correct?

hard

A. In Review model: belongs_to :product, dependent: :destroyIn Product model: has_many :reviews

B. In Review model: belongs_to :productIn Product model: has_many :reviews, dependent: :destroy

C. In Review model: has_many :productIn Product model: belongs_to :reviews, dependent: :destroy

D. In Review model: belongs_to :productIn Product model: has_many :reviews, dependent: :nullify

Solution

1. Step 1: Assign belongs_to in child model

   The Review model should have belongs_to :product to link each review to one product.

2. Step 2: Use has_many with dependent option in parent

   The Product model should have has_many :reviews, dependent: :destroy to delete reviews when product is deleted.

3. Final Answer:

   Review: belongs_to :product; Product: has_many :reviews, dependent: :destroy -> Option B

4. Quick Check:

   dependent: :destroy goes on has_many side [OK]

Hint: Put dependent: :destroy on has_many side to delete children [OK]

Common Mistakes:

• Putting dependent: :destroy on belongs_to side
• Mixing up has_many and belongs_to
• Using dependent: :nullify when deletion is wanted