What is post_delete signal in Django: Explanation and Example

The post_delete signal in Django is triggered right after a model instance is deleted from the database. It allows you to run custom code automatically after an object is removed, such as cleaning up related files or logging the deletion.

How It Works

Imagine you have a to-do list app and when you delete a task, you want to also remove any files or notes linked to that task. The post_delete signal acts like a notification that tells your app, "Hey, this task was just deleted!" right after the deletion happens.

In Django, signals are like messengers that let different parts of your app talk to each other without being tightly connected. The post_delete signal is sent automatically by Django after an object is removed from the database, so you can listen for it and run your own code in response.

This helps keep your code organized and lets you react to deletions in a clean way, like cleaning up files, updating counters, or sending alerts.

Example

This example shows how to use the post_delete signal to print a message when a Book object is deleted.

python

from django.db import models
from django.db.models.signals import post_delete
from django.dispatch import receiver

class Book(models.Model):
    title = models.CharField(max_length=100)

@receiver(post_delete, sender=Book)
def book_deleted(sender, instance, **kwargs):
    print(f'Book titled "{instance.title}" was deleted.')

Output

Book titled "Django Basics" was deleted.

When to Use

Use the post_delete signal when you need to perform actions immediately after an object is deleted. Common cases include:

• Deleting files or images linked to the deleted object to avoid leftover files.
• Updating related data or counters that depend on the deleted object.
• Logging or auditing deletions for tracking changes.
• Sending notifications or alerts when important data is removed.

This signal is helpful when you want to keep your database and related resources clean and consistent without mixing deletion logic inside your main code.

Key Points

• post_delete runs after an object is deleted from the database.
• It helps keep cleanup or follow-up tasks separate from main deletion code.
• You connect functions to this signal using the @receiver decorator or post_delete.connect().
• It receives the deleted instance, so you can access its data before it disappears.
• Useful for deleting related files, updating other models, or logging.

Key Takeaways

The post_delete signal triggers right after a model instance is deleted in Django.

Use it to run cleanup or follow-up code like deleting files or logging deletions.

Connect your function to post_delete with the @receiver decorator for clean code.

You get access to the deleted object’s data before it’s fully gone.

It helps keep your app organized by separating deletion side effects from main logic.