#18080: @transaction.commit_manually plus context processors doesn't work well
-------------------------------+--------------------------------------
Reporter: jstpierre@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.3
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Jasper St. Pierre <jstpierre@…>):
It could be considered a documentation issue, but the problem is really
apparent when mixing and matching external applications - one application
that uses commit_manually may not use an internal function.
A solution may be to "disable" transactions when in a call to render, and
restore it after the call (instead of an is_automatic boolean, make it a
stack, make transaction.commit_manually push onto the stack, push onto the
stack while rendering templates and evaluating context processors).
--
Ticket URL: <https://code.djangoproject.com/ticket/18080#comment:2>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
