#23325: InterfaceError: connection already closed in PostreSQL
-------------------------------------+-------------------------------------
Reporter: aivus | Owner:
Type: Bug | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: InterfaceError, | Unreviewed
postgresql | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Why do you think this is a bug in Django? How do you expect Django to
react when the database terminates the connection?
--
Ticket URL: <https://code.djangoproject.com/ticket/23325#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 [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/063.7f10ce3e2fe152097e0f7ddf6e1af8ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
