#15176: History view of AdminSite doesn't take in account user defined queryset
------------------------------------------------+---------------------------
Reporter: t2y | Owner: nobody
Status: new | Milestone: 1.3
Component: django.contrib.admin | Version: 1.2
Resolution: | Keywords: multi-db
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 1
Patch needs improvement: 0 |
------------------------------------------------+---------------------------
Comment (by anonymous):
I actually feel divided about this. The history is supposed to show all
the things that have been changed/added/deleted in the past. Using a
custom queryset means that the history may change over time, which seem
kind of weird. I do recognise that there might be cases where we do want a
custom queryset to be used, but I also think that in some other cases we
might actually want the default one to be used. So I'd be in favour of a
more granular system for the history view.
--
Ticket URL: <http://code.djangoproject.com/ticket/15176#comment:2>
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.
