#27074: connection.is_usable() raises AttributeError after the connection is
closed
-------------------------------------+-------------------------------------
Reporter: cjerdonek | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
This is a private API that Django primarily calls inside an `if
self.connection is not None:` block (and secondarily in testing tools
where database connection breakage isn't a concern and will abort tests in
general). For this reason, I don't expect this issue to appear through the
use of public APIs.
I'm -0 on making that change but I understand that we might have to add a
useless check just to stop these bugs reports. The performance impact will
be negligible.
--
Ticket URL: <https://code.djangoproject.com/ticket/27074#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/067.eba50979c045aa18fbffdb5f75eddba4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
