#29257: If creation of a db cursor fails, the resulting traceback is misleading
-------------------------------------+-------------------------------------
Reporter: Jerome Leclanche | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chetan Khanna):
Hey!
Sorry I forgot about this one. So I fixed a patch a bit by adding an
`else` clause to the try block in the proposed patch, and all tests pass
on current master. However, I am not sure how would one go testing about
this patch. The way I reproduced this issue was by creating a test app and
then intentionally making the schema out of sync. I don't think it's
possible to imitate that when running the test suite.
--
Ticket URL: <https://code.djangoproject.com/ticket/29257#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/068.846e962e9d8647c9736360f5fae17287%40djangoproject.com.
