Changes between Initial Version and Version 1 of Ticket #23055
- Timestamp:
- Jul 17, 2014, 3:52:56 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #23055 – Description
initial v1 1 If one is using a ModelAdmin with a custom `get_queryset()` method e.g as described in https://docs.djangoproject.com/en/1.7/topics/db/multi-db/#exposing-multiple-databases-in-django-s-admin-interface to handle routing of models hosted in a multi-DB setup, displaying the change list works as expected.1 If one is using a ModelAdmin with a custom `get_queryset()` method (e.g. as described in https://docs.djangoproject.com/en/1.7/topics/db/multi-db/#exposing-multiple-databases-in-django-s-admin-interface to handle routing of models hosted in a multi-DB setup), displaying the change list works as expected. 2 2 3 But when usage of the `list_filter` feature is added, a DB error is generated reporting that no table object for the model a hand is found in the default Django DB.3 But when usage of the `list_filter` feature is added, a DB error is generated reporting that no table object for the model at hand is found in the default Django DB. 4 4 5 5 This is because the filter machinery doesn't use the custom ModelAdmin-dictated !QuerySet but the model's default manager `all()` method: