#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 | -------------------------------------+------------------------------------- Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: assigned => closed * resolution: => fixed Comment: In [changeset:"8176150850b2e34b2afe1dc107e184eb4c6cd668"]: {{{ #!CommitTicketReference repository="" revision="8176150850b2e34b2afe1dc107e184eb4c6cd668" Fixed #21202 -- Maintained atomicity when the server disconnects. Thanks intgr for the report. This commit doesn't include a test because I don't know how to emulate a database disconnection in a cross-database compatible way. Also simplified a 'backends' test that was constrained by this problem. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/21202#comment:9> 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.9aa919144d46f8f0f70c9492d8fa8d3e%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.