#21202: Atomic masks fatal database errors and instead propagates "connection
already closed"
-------------------------------------+-------------------------------------
Reporter: intgr | Owner: aaugustin
Type: | Status: closed
Cleanup/optimization | Version:
Component: Database layer | 1.6-beta-1
(models, ORM) | Resolution: fixed
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 Aymeric Augustin <aymeric.augustin@…>):
In [changeset:"746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3"]:
{{{
#!CommitTicketReference repository=""
revision="746cded010c7ba3e2bf2df4cde32dcc9b75cb0d3"
[1.6.x] Fixed #22321 -- Wrapped exceptions in _set_autocommit.
Refs #21202.
Backport of 3becac84 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21202#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/063.3c406eb735206d9f088370d063c6bf54%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
