#33280: Migration with django-database-view don't work with multiple databases.
-------------------------------------+-------------------------------------
Reporter: razielvamp666 | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: orm migration | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
> But, Is I will wrong if I say:
>
> 1. Django support multiple databases
> 2. `django/db/models/sql/query.py` not support multiple databases
because it uses `DEFAULT_DB_ALIAS` and no matter how and when it run.
Result will be always same for non `default` DB
> 3. `django/db/models/sql/query.py` is a standard part of Django
> 4. standard part of Django not support multiple databases
> 5. => Django not support multiple databases (at least for all features)
>
> Isn't this a kind of bug?
Using `DEFAULT_DB_ALIAS` is not always against supporting multiple
databases, sometimes is adequate. It's not always easy, feasible, or
necessary to pass a current connection. You're making too strong
assumptions. Also, as far as I'm concerned we don't claim that Django
support interacting with multiple databases everywhere, see
[https://docs.djangoproject.com/en/stable/topics/db/multi-db/#multiple-
databases docs].
--
Ticket URL: <https://code.djangoproject.com/ticket/33280#comment:6>
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/071.d39acdc9704c72974ffb1dce09824785%40djangoproject.com.
