Dependent destroy and nullify in Ruby on Rails - Mini Project: Build & Apply

Dependent destroy and nullify in Rails associations

📖 Scenario: You are building a simple blog application where each Author can have many Posts. When an author is deleted, you want to control what happens to their posts.

🎯 Goal: Learn how to use dependent: :destroy and dependent: :nullify in Rails models to manage associated records when the parent record is deleted.

📋 What You'll Learn

Create an Author model with a has_many :posts association

Create a Post model with a belongs_to :author association

Add dependent: :destroy to the Author model association

Add dependent: :nullify to the Author model association

Understand the difference in behavior when deleting an author

💡 Why This Matters

🌍 Real World

Managing data relationships in web apps is common. Knowing how to control what happens to related data when deleting records helps keep data clean and consistent.

💼 Career

Rails developers often work with associations and must understand dependent options to avoid data loss or orphaned records.

1

Create Author and Post models with associations

Create a Rails model called Author with a has_many :posts association and a Rails model called Post with a belongs_to :author association.

Ruby on Rails

# Create Author and Post models with associations

class Author < ApplicationRecord
  # Your code here
end

class Post < ApplicationRecord
  # Your code here
end

Hint

Use has_many :posts inside the Author model and belongs_to :author inside the Post model.

2

Add dependent: :destroy to Author's posts association

Modify the Author model to add dependent: :destroy to the has_many :posts association to delete posts when an author is deleted.

Ruby on Rails

class Author < ApplicationRecord
  # Add dependent: :destroy to posts association
  has_many :posts, dependent: :destroy
end

class Post < ApplicationRecord
  belongs_to :author
end

Hint

Add dependent: :destroy inside the has_many :posts association in the Author model.

3

Change dependent option to :nullify

Change the dependent option in the Author model's has_many :posts association from :destroy to :nullify so posts are not deleted but their author_id is set to NULL when an author is deleted.

Ruby on Rails

class Author < ApplicationRecord
  # Change dependent option to :nullify
  has_many :posts, dependent: :nullify
end

class Post < ApplicationRecord
  belongs_to :author
end

Hint

Replace dependent: :destroy with dependent: :nullify in the has_many :posts association.

4

Add optional: true to Post's belongs_to association

Modify the Post model's belongs_to :author association to add optional: true so posts can exist without an author after nullification.

Ruby on Rails

class Author < ApplicationRecord
  has_many :posts, dependent: :nullify
end

class Post < ApplicationRecord
  # Add optional: true to belongs_to association
  belongs_to :author, optional: true
end

Hint

Add optional: true inside the belongs_to :author association in the Post model.

Practice

1. What does dependent: :destroy do in a Rails model association?

easy

A. Deletes associated records when the parent record is deleted.

B. Sets associated records' foreign keys to null when the parent is deleted.

C. Prevents deletion of the parent record if associated records exist.

D. Copies associated records to a backup table before deletion.

Solution

1. Step 1: Understand the role of dependent option

   The dependent option in Rails associations controls what happens to associated records when the parent is deleted.

2. Step 2: Identify behavior of :destroy

   The :destroy option deletes all associated records automatically when the parent record is deleted.

3. Final Answer:

   Deletes associated records when the parent record is deleted. -> Option A

4. Quick Check:

   dependent: :destroy = deletes associated records [OK]

Hint: Destroy deletes children; nullify just clears foreign keys [OK]

Common Mistakes:

• Confusing :destroy with :nullify behavior
• Thinking :destroy prevents parent deletion
• Assuming it backs up records before deletion

2. Which is the correct syntax to set an association to nullify dependent records in Rails?

easy

A. has_many :comments, dependent: :delete_all

B. has_many :comments, dependent: :remove

C. has_many :comments, dependent: :nullify

D. has_many :comments, dependent: :destroy_all

Solution

1. Step 1: Recall valid dependent options in Rails

   Rails supports :destroy, :delete_all, and :nullify as valid dependent options.

2. Step 2: Identify the option that sets foreign keys to null

   dependent: :nullify sets the foreign keys of associated records to null instead of deleting them.

3. Final Answer:

   has_many :comments, dependent: :nullify -> Option C

4. Quick Check:

   dependent: :nullify = sets foreign keys to null [OK]

Hint: Use :nullify to keep records but clear foreign keys [OK]

Common Mistakes:

• Using :destroy_all which is invalid
• Confusing :delete_all with :nullify
• Using non-existent :remove option

3. Given the models:

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

class Comment < ApplicationRecord
  belongs_to :post, optional: true
end

What happens to comments when a post is deleted?

medium

A. Comments remain but their post_id is set to null.

B. All comments are deleted from the database.

C. Comments remain unchanged with the same post_id.

D. An error occurs because comments must belong to a post.

Solution

1. Step 1: Analyze the dependent option in Post model

   The dependent: :nullify option means when a post is deleted, associated comments' foreign keys (post_id) are set to null.

2. Step 2: Check if comments can have null post_id

   The belongs_to :post, optional: true allows comments to exist without a post, so setting post_id to null is valid.

3. Final Answer:

   Comments remain but their post_id is set to null. -> Option A

4. Quick Check:

   dependent: :nullify + optional: true = nullify foreign keys [OK]

Hint: Nullify keeps records but clears foreign keys if optional true [OK]

Common Mistakes:

• Assuming comments get deleted with post
• Ignoring optional: true and expecting errors
• Thinking comments keep old post_id after deletion

4. Identify the error in this Rails model code:

class User < ApplicationRecord
  has_many :posts, dependent: :nullify
end

class Post < ApplicationRecord
  belongs_to :user
end

medium

A. belongs_to should be has_many in Post model.

B. No error; code works as expected.

C. dependent: :nullify is invalid syntax for has_many.

D. Posts cannot have null user_id because belongs_to is not optional.

Solution

1. Step 1: Understand dependent: :nullify effect

   It sets foreign keys of associated posts to null when a user is deleted.

2. Step 2: Check belongs_to association in Post

   belongs_to :user by default requires user_id to be present (not null). Since it's not marked optional, nullifying user_id causes validation or DB errors.

3. Final Answer:

   Posts cannot have null user_id because belongs_to is not optional. -> Option D

4. Quick Check:

   dependent: :nullify requires optional belongs_to [OK]

Hint: Use optional: true with nullify to avoid errors [OK]

Common Mistakes:

• Assuming nullify works without optional: true
• Thinking dependent: :nullify is invalid syntax
• Confusing belongs_to with has_many in Post

5. You have a Library model with many Books. You want to delete a library and automatically delete all its books. But if a Book has Reviews, you want to keep the reviews but remove the book reference (set book_id to null). Which setup correctly achieves this?

hard

A. Library has_many :books, dependent: :destroy; Book has_many :reviews, dependent: :destroy; Review belongs_to :book, optional: true

B. Library has_many :books, dependent: :destroy; Book has_many :reviews, dependent: :nullify; Review belongs_to :book, optional: true

C. Library has_many :books, dependent: :nullify; Book has_many :reviews, dependent: :destroy; Review belongs_to :book

D. Library has_many :books, dependent: :nullify; Book has_many :reviews, dependent: :nullify; Review belongs_to :book

Solution

1. Step 1: Set Library to delete all books on deletion

   Using dependent: :destroy on has_many :books deletes all books when a library is deleted.

2. Step 2: Set Book to nullify reviews instead of deleting

   Using dependent: :nullify on has_many :reviews keeps reviews but sets their book_id to null.

3. Step 3: Allow reviews to have null book_id

   Marking belongs_to :book, optional: true in Review allows book_id to be null without errors.

4. Final Answer:

   Library has_many :books, dependent: :destroy; Book has_many :reviews, dependent: :nullify; Review belongs_to :book, optional: true -> Option B

5. Quick Check:

   destroy deletes children; nullify clears foreign keys with optional true [OK]

Hint: Destroy parents, nullify grandchildren with optional belongs_to [OK]

Common Mistakes:

• Using nullify on library-books deletes nothing
• Destroying reviews deletes data you want to keep
• Not setting optional: true on Review's belongs_to