Why On_delete options (CASCADE, PROTECT, SET_NULL) in Django? - Purpose & Use Cases

The Big Idea

What if deleting one item could silently break your whole database without warning?

The Scenario

Imagine you have a list of books linked to authors in a database. When you delete an author manually, you must remember to update or remove all their books too, or your data will be messy and broken.

The Problem

Manually handling related data deletions is slow and risky. You might forget to delete or update linked records, causing errors or inconsistent data that confuse users and crash your app.

The Solution

Django's on_delete options like CASCADE, PROTECT, and SET_NULL automatically manage related data when you delete an object, keeping your database clean and consistent without extra work.

Before vs After

✗ Before

if author_deleted:
    for book in books:
        if book.author == author:
            delete_or_update(book)

✓ After

author = Author.objects.get(id=1)
author.delete()  # related books handled automatically by on_delete

What It Enables

This lets you safely delete or protect related data with simple rules, so your app stays reliable and your code stays clean.

Real Life Example

When an author is removed from a library system, all their books can be deleted automatically (CASCADE), or deletion can be blocked if books exist (PROTECT), or books can keep their record but lose the author link (SET_NULL).

Key Takeaways

Manual deletion of related data is error-prone and tedious.

on_delete options automate data consistency when deleting linked records.

CASCADE, PROTECT, and SET_NULL cover common real-world needs safely and simply.

Practice

1. What does the on_delete=models.CASCADE option do in Django models?

easy

A. Deletes related objects automatically when the referenced object is deleted.

B. Prevents deletion of the referenced object if related objects exist.

C. Sets the related field to null instead of deleting the object.

D. Raises an error if the related object is missing.

Solution

1. Step 1: Understand CASCADE behavior

   The CASCADE option means when the referenced object is deleted, all related objects are also deleted automatically.

2. Step 2: Compare with other options

   Unlike PROTECT or SET_NULL, CASCADE deletes dependent objects without error or nullifying fields.

3. Final Answer:

   Deletes related objects automatically when the referenced object is deleted. -> Option A

4. Quick Check:

   CASCADE = auto-delete related objects [OK]

Hint: CASCADE means delete all linked items automatically [OK]

Common Mistakes:

• Confusing CASCADE with PROTECT which blocks deletion
• Thinking CASCADE sets fields to null instead of deleting
• Assuming CASCADE raises errors on deletion

2. Which of the following is the correct syntax to use SET_NULL in a Django ForeignKey field?

easy

A. models.ForeignKey(OtherModel, on_delete=models.SET_NULL)

B. models.ForeignKey(OtherModel, on_delete=models.SET_NULL, null=True)

C. models.ForeignKey(OtherModel, on_delete=models.SET_NULL, blank=True)

D. models.ForeignKey(OtherModel, on_delete=models.SET_NULL, default=None)

Solution

1. Step 1: Recognize SET_NULL requires nullable field

   Using SET_NULL requires the field to allow null values, so null=True must be set.

2. Step 2: Check each option for null=True

   Only models.ForeignKey(OtherModel, on_delete=models.SET_NULL, null=True) includes null=True along with SET_NULL, making it valid syntax.

3. Final Answer:

   models.ForeignKey(OtherModel, on_delete=models.SET_NULL, null=True) -> Option B

4. Quick Check:

   SET_NULL needs null=True [OK]

Hint: SET_NULL needs null=True to allow null values [OK]

Common Mistakes:

• Omitting null=True with SET_NULL causes errors
• Confusing blank=True with null=True for database nulls
• Using default=None without null=True

3. Given the models:

class Author(models.Model):
    name = models.CharField(max_length=100)

class Book(models.Model):
    author = models.ForeignKey(Author, on_delete=models.PROTECT)
    title = models.CharField(max_length=100)

What happens if you try to delete an Author who has related Book entries?

medium

A. The author is deleted but books remain with invalid author references.

B. The author is deleted and all related books are deleted too.

C. The author is deleted and the book's author field is set to null.

D. The deletion is blocked and raises an error.

Solution

1. Step 1: Understand PROTECT behavior

   PROTECT prevents deletion of the referenced object if related objects exist, raising an error instead.

2. Step 2: Apply to given models

   Since Book has a ForeignKey with PROTECT to Author, deleting an Author with Books will raise a ProtectedError.

3. Final Answer:

   The deletion is blocked and raises an error. -> Option D

4. Quick Check:

   PROTECT blocks deletion if related objects exist [OK]

Hint: PROTECT stops deletion if related objects exist [OK]

Common Mistakes:

• Assuming PROTECT deletes related objects like CASCADE
• Thinking PROTECT sets fields to null
• Ignoring the error raised on deletion attempt

4. Consider this model definition:

class Comment(models.Model):
    post = models.ForeignKey(Post, on_delete=models.SET_NULL)
    content = models.TextField()

What is the error in this code?

medium

A. No error, the code is correct.

B. ForeignKey cannot use SET_NULL as on_delete option.

C. Missing null=True on the ForeignKey field.

D. TextField cannot be used with ForeignKey.

Solution

1. Step 1: Check requirements for SET_NULL

   Using SET_NULL requires the ForeignKey field to allow null values by setting null=True.

2. Step 2: Identify missing null=True

   The code does not include null=True on the post field, causing an error.

3. Final Answer:

   Missing null=True on the ForeignKey field. -> Option C

4. Quick Check:

   SET_NULL needs null=True [OK]

Hint: SET_NULL requires null=True on ForeignKey [OK]

Common Mistakes:

• Assuming SET_NULL works without null=True
• Confusing TextField usage with ForeignKey
• Thinking SET_NULL is invalid on ForeignKey

5. You have two models:

class Category(models.Model):
    name = models.CharField(max_length=50)

class Product(models.Model):
    category = models.ForeignKey(Category, on_delete=models.SET_NULL, null=True)
    name = models.CharField(max_length=100)

If a Category is deleted, what happens to the related Product entries and why is this setup useful?

hard

A. Products keep their category field as null; useful to retain products without category.

B. Products are deleted automatically; useful to keep database clean.

C. Deletion is blocked; useful to prevent accidental data loss.

D. Products keep old category id; useful for historical reference.

Solution

1. Step 1: Understand SET_NULL with null=True

   When the referenced Category is deleted, the Product's category field is set to null instead of deleting the Product.

2. Step 2: Explain usefulness

   This allows products to remain in the database without a category, which is useful if products should not be deleted just because their category is removed.

3. Final Answer:

   Products keep their category field as null; useful to retain products without category. -> Option A

4. Quick Check:

   SET_NULL + null=True keeps related objects, nullifies field [OK]

Hint: SET_NULL keeps objects, sets field null to keep data [OK]

Common Mistakes:

• Assuming related products get deleted with SET_NULL
• Thinking deletion is blocked like PROTECT
• Believing old category id remains after deletion