#13412: Exposing multiple db in admin interface is limited
-------------------------------------------+--------------------------------
Reporter: idle | Owner: nobody
Status: new | Milestone:
Component: django.contrib.admin | Version: 1.2-beta
Resolution: | Keywords:
Stage: Someday/Maybe | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Someday/Maybe
* summary: Exposing multiple db in admin interface is limited
(list_filter support) => Exposing multiple db
in admin interface is limited
* needs_tests: => 0
* needs_docs: => 0
Comment:
The documentation says that the admin doesn't have explicit support for
multiple databases. Adding explicit support is an area for improvement.
Using routers, it should be possible to use multi-db and the admin for
many use cases (in particular, master-slave replication). There will
certainly be use cases that admin will have difficulty with.
I'll leave this open as a someday/maybe ticket, given that this is a
documented limitation. However, This is something that will need a
specific proposal in order to go further.
--
Ticket URL: <http://code.djangoproject.com/ticket/13412#comment:1>
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-upda...@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.
