#12767: Problem running syncdb with a multi-db router that restricts auth to a
single database
---------------------------------------------------+------------------------
Reporter: russellm | Owner: nobody
Status: new | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by russellm):
After closer inspection, I'm going to mark this someday/maybe.
The underlying problem here is that auth has foreign keys to contenttypes.
This means that you need to deal with referential integrity across
databases, which is a non-trivial problem to solve (other than the obvious
workaround of putting contenttypes on the same database as auth)
An alternative solution would be to modify the contenttypes syncdb handler
so that contenttypes can be synchronized onto multiple databases. However,
this would require lots of extra logic to ensure that databases remained
in sync, including ensuring that primary key allocation for content types
is consistent between databases.
However, I will make a change to the multi-db docs -- they currently
suggest that routers can be used to put auth onto a separate database, and
while this is technically true, it won't be true for many uses in
practice. Better to avoid the implication altogether.
--
Ticket URL: <http://code.djangoproject.com/ticket/12767#comment:5>
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.
