#11015: django-1.0.2 does not catch the exception that database backend first
close
the db connection.
---------------------------------------------------+------------------------
Reporter: qingran | Owner: nobody
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by gkulewski):
Another case, possibly similar and not involving reversion.
Model called URL has generic foreign key to model Resource.
Model Resource has reverse generic relation back to model URL.
Model Foo has normal foreign key to model URL.
Then I am trying to delete Resource instance (via admin). This silently
(as in admin does not warn about it) cascades to URLs connected to it (/me
thinks the admin should warn about it...). And this breaks because django
forgot to cascade to Foo referencing that URL. Boom (a silent one, in
pgsql, not reported outside by django for some strange reason). And later
big boom because something didn't recover nicely from the first error.
Result: application can't make any SQL queries anymore.
Thinking more about it, previously described case may be a special case of
this one (not cascading correctly, reversion probably uses some generic
relations too or something). And bad error recovery after errors repoted
by pgsql is another problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/11015#comment:9>
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.
