Association callbacks in Ruby on Rails

Introduction

Association callbacks let you run code automatically when related records change. This helps keep your data connected and actions in sync.

When you want to run code right after adding or removing an associated record.

When you need to update or clean up related data automatically.

When you want to trigger notifications or logging when associations change.

When you want to enforce rules or validations on related records during save or destroy.

When you want to keep counters or caches updated based on association changes.

Syntax

Ruby on Rails

has_many :comments, after_add: :method_name, after_remove: :method_name

# method_name is a symbol for a method in the model

You can use after_add and after_remove callbacks on associations like has_many or has_and_belongs_to_many.

The callback method receives the associated record as an argument.

Examples

This runs notify_comment_added after a comment is added to a post.

Ruby on Rails

class Post < ApplicationRecord
  has_many :comments, after_add: :notify_comment_added

  def notify_comment_added(comment)
    puts "New comment added: #{comment.body}"
  end
end

This runs log_role_removed after a role is removed from a user.

Ruby on Rails

class User < ApplicationRecord
  has_many :roles, after_remove: :log_role_removed

  def log_role_removed(role)
    puts "Role removed: #{role.name}"
  end
end

Sample Program

This example shows an Author model with has_many :books association. It uses after_add and after_remove callbacks to print messages when books are added or removed.

When you add books to the author's collection, it announces the new book. When you remove a book, it announces the removal.

Ruby on Rails

class Author < ApplicationRecord
  has_many :books, after_add: :announce_new_book, after_remove: :announce_removed_book

  def announce_new_book(book)
    puts "Author #{name} added a new book titled '#{book.title}'."
  end

  def announce_removed_book(book)
    puts "Author #{name} removed the book titled '#{book.title}'."
  end
end

class Book < ApplicationRecord
  belongs_to :author
end

# Simulate adding and removing books
author = Author.new(name: "Alice")
book1 = Book.new(title: "Ruby Basics")
book2 = Book.new(title: "Rails Advanced")

# Add books
author.books << book1
author.books << book2

# Remove a book
author.books.delete(book1)

Important Notes

Callbacks run only when you modify the association collection, not when you save the parent or child alone.

Use callbacks carefully to avoid unexpected side effects or performance issues.

Summary

Association callbacks run code automatically when related records are added or removed.

Use after_add and after_remove options on associations like has_many.

They help keep related data and actions in sync without extra manual code.

Practice

1. What is the purpose of after_add and after_remove callbacks in Rails associations?

easy

A. To define database indexes on associations

B. To validate the presence of associated records

C. To preload associated records for performance

D. To run code automatically when related records are added or removed

Solution

1. Step 1: Understand association callbacks

   Rails provides after_add and after_remove callbacks to trigger code when associated records change.

2. Step 2: Identify their purpose

   These callbacks run automatically when you add or remove related records, helping keep data in sync.

3. Final Answer:

   To run code automatically when related records are added or removed -> Option D

4. Quick Check:

   Association callbacks = automatic code on add/remove [OK]

Hint: Callbacks run code on add/remove related records [OK]

Common Mistakes:

• Confusing callbacks with validations
• Thinking callbacks preload data
• Assuming callbacks define indexes

2. Which is the correct syntax to add an after_add callback to a has_many association named comments in a Rails model?

easy

A. has_many :comments, after_add: :notify_comment_added

B. has_many :comments, after_add => :notify_comment_added

C. has_many :comments do after_add :notify_comment_added end

D. has_many :comments, callback_after_add: :notify_comment_added

Solution

1. Step 1: Recall correct hash syntax for options

   Rails uses symbol keys with colon and value pairs like after_add: :method_name.

2. Step 2: Match syntax to association

   The correct syntax is has_many :comments, after_add: :notify_comment_added.

3. Final Answer:

   has_many :comments, after_add: :notify_comment_added -> Option A

4. Quick Check:

   Use colon syntax for options in associations [OK]

Hint: Use colon syntax for options in associations [OK]

Common Mistakes:

• Using hash rocket => instead of colon :
• Trying to define callback inside block
• Using wrong option name like callback_after_add

3. Given the following code, what will be printed when a new comment is added to a Post?

class Post < ApplicationRecord
  has_many :comments, after_add: :log_comment_added

  def log_comment_added(comment)
    puts "Comment added: #{comment.body}"
  end
end

post = Post.new
post.comments << Comment.new(body: 'Nice post!')

medium

A. No output

B. Comment added: Nice post!

C. Error: undefined method log_comment_added

D. Comment added:

Solution

1. Step 1: Understand after_add callback behavior

   The after_add callback calls log_comment_added with the new comment when added.

2. Step 2: Check the method output

   The method prints "Comment added: " plus the comment's body, which is "Nice post!".

3. Final Answer:

   Comment added: Nice post! -> Option B

4. Quick Check:

   after_add calls method with new record [OK]

Hint: after_add calls method with added record [OK]

Common Mistakes:

• Expecting no output
• Thinking callback is not triggered on << operator
• Assuming method is missing error

4. Identify the error in this Rails model code using after_remove callback:

class User < ApplicationRecord
  has_many :posts, after_remove: :notify_post_removed

  def notify_post_removed
    puts 'Post removed'
  end
end

medium

A. The callback method must accept the removed record as an argument

B. The callback name should be after_remove_post

C. The after_remove option is not valid for has_many

D. The method should be private

Solution

1. Step 1: Check callback method signature

   Callbacks like after_remove receive the removed record as an argument.

2. Step 2: Compare method definition

   The method notify_post_removed has no parameters, so it will cause an error.

3. Final Answer:

   The callback method must accept the removed record as an argument -> Option A

4. Quick Check:

   Callback methods need removed record argument [OK]

Hint: Callback methods must accept the changed record argument [OK]

Common Mistakes:

• Defining callback method without parameters
• Using invalid callback option name
• Thinking method visibility causes error

5. You want to track when tags are added or removed from an Article model using has_many :tags. You want to update a counter on Article each time tags change. Which is the best way to implement this using association callbacks?

hard

A. Use before_save callback on Article to count tags

B. Override the tags= setter method to update the counter

C. Use after_add and after_remove callbacks on has_many :tags to update the counter method

D. Manually call a method to update the counter after changing tags

Solution

1. Step 1: Understand the goal

   You want to update a counter automatically when tags are added or removed.

2. Step 2: Choose appropriate callback

   after_add and after_remove on has_many :tags run code exactly when tags change.

3. Step 3: Compare other options

   Overriding setter or using before_save is less direct and can miss changes; manual calls are error-prone.

4. Final Answer:

   Use after_add and after_remove callbacks on has_many :tags to update the counter method -> Option C

5. Quick Check:

   Use association callbacks for automatic related record updates [OK]

Hint: Use after_add and after_remove for automatic updates [OK]

Common Mistakes:

• Overriding setter unnecessarily
• Using before_save which may miss association changes
• Forgetting to automate updates