#10889: ModelAdmin calls .log_deletion after deletion, causing invalid object_id --------------------------+------------------------------------------------- Reporter: jdunck | Owner: nobody Status: new | Milestone: 1.1 Component: Contrib apps | Version: 1.1-beta-1 Keywords: | Stage: Unreviewed Has_patch: 1 | --------------------------+------------------------------------------------- When an object is deleted, its PK value is set to None. Unfortunately, ModelAdmin calls log_deletion (which results in a LogEntry) after object.delete, so that LogEntry's with DELETION action_flag have u'None' as their PK.
This is less than useful, since I sometimes what to trace the full history of an object through LogEvent, and object_repr isn't really enough to do that. -- Ticket URL: <http://code.djangoproject.com/ticket/10889> 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
