#15176: History view of AdminSite doesn't take in account user defined queryset -----------------------------+---------------------------------------------- Reporter: t2y | Owner: Status: new | Milestone: 1.3 Component: ORM aggregation | Version: 1.2 Keywords: multi-db | Stage: Unreviewed Has_patch: 1 | -----------------------------+---------------------------------------------- I found a bug which does not show history view in AdminSite when I defined a queryset for multi-db.
# see also:[[BR]] [http://docs.djangoproject.com/en/dev/topics/db/multi-db/#exposing- multiple-databases-in-django-s-admin-interface] The history_view method of django.contrib.admin.ModelAdmin give a model object to get_object_or_404 as an argument. In that case, normal queryset of the model is used even if user defined custom queryset for the model. It means that the history view isn't showed for multi-db since it define custom queryset. I made a patch, but I have no idea for making tests code. I only tested after I did some table operation, and I confirmed the history view. Additionally, you might wonder about the LogEntry(django_admin_log). I think it's no problem since I can handle LogEntry to read/write with db- router. -- Ticket URL: <http://code.djangoproject.com/ticket/15176> 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.
