Why associations connect models in Ruby on Rails - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use associations between models in Rails?

What is the main reason Rails uses associations to connect models?

A To enforce strict data types on model attributes

B To easily retrieve related data without writing complex SQL queries

C To automatically generate user interface elements

D To speed up the Rails server startup time

💡 Hint

Think about how Rails helps you get related records.

Associations in Rails link models so you can fetch related data simply, avoiding manual SQL joins.

❓ component_behavior

intermediate

What happens when you call has_many in a model?

In Rails, what does adding has_many :comments inside a Post model do?

A Generates a new database table for comments

B Automatically deletes all comments when the post is created

C Prevents comments from being saved without a post

D Creates a method to fetch all comments related to that post

💡 Hint

Think about what has_many means in terms of data access.

The has_many association adds a method to get all related comments for a post.

❓ state_output

advanced

Output of accessing associated records

Given these models:

class Author < ApplicationRecord
  has_many :books
end

class Book < ApplicationRecord
  belongs_to :author
end

author = Author.create(name: 'Jane')
author.books.create(title: 'Book 1')
author.books.create(title: 'Book 2')

puts author.books.count

What is the output?

A 2

B 1

C 0

D Raises an error

💡 Hint

How many books did we add to the author?

Two books were created for the author, so author.books.count returns 2.

📝 Syntax

advanced

Identify the correct association syntax

Which option correctly sets up a one-to-one association where a User has one Profile?

A

class User < ApplicationRecord
  has_one :profile
end

class Profile < ApplicationRecord
  belongs_to :user
end

B

class User < ApplicationRecord
  belongs_to :profile
end

class Profile < ApplicationRecord
  has_one :user
end

C

class User < ApplicationRecord
  has_many :profile
end

class Profile < ApplicationRecord
  belongs_to :user
end

D

class User < ApplicationRecord
  has_one :profiles
end

class Profile < ApplicationRecord
  belongs_to :user
end

💡 Hint

Remember singular vs plural and which side owns the foreign key.

Option A correctly uses has_one and belongs_to with singular names.

🔧 Debug

expert

Why does accessing an association raise an error?

Given these models:

class Order < ApplicationRecord
  has_many :items
end

class Item < ApplicationRecord
  belongs_to :order
end

order = Order.new
order.items.first.name

Why does this code raise an error?

A Because <code>belongs_to</code> is missing in the Item model

B Because <code>has_many</code> requires a foreign key in the Order model

C Because <code>order</code> is not saved, so <code>items</code> association is empty and <code>first</code> returns nil, causing <code>nil.name</code> error

D Because <code>order.items</code> returns a string, not a collection

💡 Hint

What happens when you call a method on nil?

Since order is not saved, it has no items. Calling first returns nil, then name on nil raises NoMethodError.