#10889: ModelAdmin calls .log_deletion after deletion, causing invalid object_id
-------------------------------------------+--------------------------------
Reporter: jdunck | Owner: nobody
Status: new | Milestone: 1.1
Component: django.contrib.admin | Version: 1.1-beta-1
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by ramiro):
Only (minor?) problem with moving the log_deletion() call to above the
actual deletion is this might leave the log event with inaccurate
information (reporting a successful action) if the obj.delete() fails for
some reason and throws an exception.
--
Ticket URL: <http://code.djangoproject.com/ticket/10889#comment:3>
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-updates@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
-~----------~----~----~----~------~----~------~--~---
