---
title: "Discussion on \"Django's post_save doesn't always\" | Hashnode"
description: "Discussion on \"Django's post_save doesn't always\". Django’s post_save methods allow execution of custom code on an insert or update of a record after the save method is called.\nThe serialized object propagates through the signal handlers as the instance parameter which is eventually committed to the ..."
url: "https://hashnode.com/posts/djangos-postsave-doesnt-always/673ea2383a4e08580987a9dd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Django's post\_save doesn't always](https://blog.danwald.me/djangos-postsave-doesnt-always?utm_source=hashnode&utm_medium=feed)

Django’s post\_save methods allow execution of custom code on an insert or update of a record after the save method is called. The serialized object propagates through the signal handlers as the instance parameter which is eventually committed to the ...

Nov 21, 2024 · 1 min read · blog.danwald.me  
Read the article

-   [#django](https://hashnode.com/tag/django)
-   [#djangosignals](https://hashnode.com/tag/djangosignals)
-   [#inconsistency](https://hashnode.com/tag/inconsistency)
-   [#transactions](https://hashnode.com/tag/transactions)

## Written by

[Danny Crasto](https://hashnode.com/@danwald)

@danwald · dubai, uae

  
[View profile](https://hashnode.com/@danwald)

backend/cloud engineer | mentor | pythonista

I am developer/code-reviewer/debugger/bug-fixer/architect/teacher/builder from dubai, uae

## Responses

Markdown supported · ⌘↵ to post

No responses yet.