#36741: Explain why pre_save/post_save signals are skipped when using
QuerySet.update()
-------------------------------------+-------------------------------------
Reporter: Lam Phung | Type:
| Cleanup/optimization
Status: new | Component:
| Documentation
Version: 5.2 | Severity: Normal
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
The documentation for QuerySet.update() briefly mentions that the model’s
save() method is not called and pre_save/post_save signals are not sent.
However, the docs do not explain why this matters or what those signals
normally do. This could be confusing for new contributors who are
understanding the difference between update(), and manually calling save()
on each object. The current documentation could be updated to include
information on why selecting the wrong method could disrupt current logic,
or when it is safe/unsafe to use update().
--
Ticket URL: <https://code.djangoproject.com/ticket/36741>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a95a778d4-0e3fd659-2ed9-4a38-8398-d6cbf5676ecc-000000%40eu-central-1.amazonses.com.
