#29557: add on_commit decorator
-------------------------------------+-------------------------------------
Reporter: obayemi | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: transaction | Triage Stage:
on_commit decorator | Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
> isn't this why signals are implemented anyway?
Not really. There's a good article on it here:
[https://lincolnloop.com/blog/django-anti-patterns-signals/ Django Anti-
Patterns: Signals]
You really are better off explicitly calling the handler in the places you
need it. (They'll be few in reality.)
However, that's an off-topic discussion for here... 🙂
--
Ticket URL: <https://code.djangoproject.com/ticket/29557#comment:8>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.6026713722ceb3c5258a934b4edee399%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
