#11015: django-1.0.2 does not catch the exception that database backend first
close
the db connection.
---------------------------------------------------+------------------------
Reporter: qingran | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: duplicate | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by kmtracey):
I've tried your scenario on current trunk, and can't recreate most of what
you list above.
First, the confirmation page now does list that the associated URL model
is going to be deleted. This was likely done by the fix for #6191.
Second, I don't get any hiding of DB errors. With debug on I get a debug
page with full details of the error. With debug off I get a server error
page.
Perhaps because of the second item, I don't see any error related to
trying to close an already-closed connection. I assume that is what you
mean by "not recovering after db error"? If not please explain what you
mean because I'm having hard time connecting what you are reporting now
with the original report.
--
Ticket URL: <http://code.djangoproject.com/ticket/11015#comment:12>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
