#21461: Add pre_update and post_update signals
-------------------------------------+-------------------------------------
Reporter: loic84 | Owner: loic84
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by loic84):
@shai you are totally right, the limitation on changing pk is something we
already discussed but I agree it needs to be documented.
At this point @akaariai and I are not sure about how to proceed with this
patch. Do we only introduce `post_signal`? Is there value in the
`pre_signal` as currently implemented? Are there enough people who want
update signals at all?
Opinion welcome.
--
Ticket URL: <https://code.djangoproject.com/ticket/21461#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.768d2d071889fa4874499ea7c423d9d1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
