#27164: Multiple problems with multiple database docs for 1.8 and possibly other
versions
-------------------------------------+-------------------------------------
Reporter: michaelcoconnor | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: multiple databases | Triage Stage:
docs | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by michaelcoconnor):
Let's see you start on the rather evident--- no code examples needed
here--- contradiction between the fact that the AuthRouter() assigns all
auth models and only auth models to one database and the statement at the
bottom that "auth models — User, Group and Permission — are linked
together and linked to ContentType, so they must be stored in the same
database as ContentType." This ticket is in part about documentation,
writing--- not only about whether the given code example works or not.
That seeming conflict is in '''1.7 through to dev'''. Yes or no. Is this
not a glaring and absurd conflict (and a pain-inducing one at that for
those who are new to multiple databases)? Wouldn't the django_content_type
model end up in the second database, whereas the docs 1.7-dev all say it
must be stored in the same database as auth?
Since 1.9 discontinued support for FastCGI some hosting companies offering
shared-hosting (e.g., A2 Hosting, a "Django-friendly" company) are stalled
out at Django 1.8.7 for now. I think that you can revise the 1.8 docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/27164#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.7b8bc43046dc9ca4bf94a818db442947%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
