#21553: InterfaceError in Postgres
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.6
(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:
`InterfaceError` means that something is wrong with the database adapter
on the Python side. I'm not convinced it's safe or useful to attempt
automatically reconnecting to the database in that case.
That's why I chose to catch `DatabaseError` and not `InterfaceError`.
Could you explain your use case? In what circumstances do you receive
`InterfaceError`?
--
Ticket URL: <https://code.djangoproject.com/ticket/21553#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/067.292753f8cad8aacd13a7eed35a2f906f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
