#29257: If creation of a db cursor fails, the resulting traceback is misleading
-------------------------------------+-------------------------------------
Reporter: Jerome Leclanche | Owner: VIZZARD-X
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"c68e4adea0703354508d51895b091771b1f6ac45" c68e4ad]:
{{{#!CommitTicketReference repository=""
revision="c68e4adea0703354508d51895b091771b1f6ac45"
Fixed #29257 -- Caught DatabaseError when attempting to close a possibly
already-closed cursor.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29257#comment:14>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b94f3bc0f-f300bbc9-88d8-4dae-b920-59ca22d3dce4-000000%40eu-central-1.amazonses.com.
