#34121: Multi Databases documenation example doesn't work
-------------------------------------+-------------------------------------
Reporter: MasteroPL | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
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 Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
> Well, logically so - such table is not present in this database. But I
defined the router exactly as the documentation told me to. Therefore
based on what I see in the documentation I labeled it as a bug in this
report.
All contrib apps must be together in one database, as
[https://docs.djangoproject.com/en/stable/topics/db/multi-db/#no-cross-
database-relations cross-database relations] are not supported. It's
[https://docs.djangoproject.com/en/stable/topics/db/multi-db/#an-example
documented] on the same page:
> ''"your routers must handle the names of all apps in `INSTALLED_APPS`
before you migrate. See
[https://docs.djangoproject.com/en/stable/topics/db/multi-db/#contrib-app-
multiple-databases Behavior of contrib apps] for information about contrib
apps that must be together in one database."''
--
Ticket URL: <https://code.djangoproject.com/ticket/34121#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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070184138ebba8-23790b0a-84ae-4e56-91ac-20178db9ccb3-000000%40eu-central-1.amazonses.com.
