#21029: Schema editors leak transaction state on exception
-------------------------------------+-------------------------------------
Reporter: koniiiik | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm probably to blame for suggesting the `__enter__` / `__exit__` hack to
Andrew, but I have to say this is very bad.
If we're using this hack, we must guarantee that `__exit__` will be called
with robust exception handling.
--
Ticket URL: <https://code.djangoproject.com/ticket/21029#comment:1>
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/066.27dd4b767e691f9562fb07f5d0778fde%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
