#36228: ModelAdmin using non-default DB + RelatedOnlyFieldListFilter crashes
-------------------------------+--------------------------------------
     Reporter:  Ran Benita     |                    Owner:  (none)
         Type:  Bug            |                   Status:  closed
    Component:  contrib.admin  |                  Version:  5.1
     Severity:  Normal         |               Resolution:  invalid
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by Sarah Boyce):

 * resolution:   => invalid
 * status:  new => closed

Comment:

 Hi Ran

 As documented, the Django admin doesn't have any explicit support for
 multiple databases: https://docs.djangoproject.com/en/5.1/topics/db/multi-
 db/#exposing-multiple-databases-in-django-s-admin-interface
 I also think you might want to solve this at a Router level using
 db_for_read: https://docs.djangoproject.com/en/5.1/topics/db/multi-
 db/#db_for_read

 If you need support, please use one of our user support channels from
 [https://docs.djangoproject.com/en/dev/faq/help/#how-do-i-do-x-why-
 doesn-t-y-work-where-can-i-go-to-get-help this link].
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36228#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019565a00aec-9f01959b-c502-43a1-a0a3-f85dce425c86-000000%40eu-central-1.amazonses.com.

Reply via email to