#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 razielvamp666):

 Replying to [comment:1 Mariusz Felisiak]:
 > Thanks for this report. However a lot of things happen outside of
 Django, you have many 3rd-party packages, a custom `Operation` in
 migrations, etc. The main issue is that you're using the `query` attribute
 to generate an SQL which is not recommended, documented, or supported.
 Moreover, this helper has issues with parameters (see #25705) and doesn't
 work when the `default` database is empty (see #25947). I'm not marking
 this as a duplicate of #25947 as fixing it will not make `.query` the
 recommended way to generate an SQL. I would use a raw SQL in your case.
 >

 Thank you for answer.
 Sorry, I didn't notice that was used little bit our code too. Not just
 standard libraries.

 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?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33280#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.115273a8e4dd0f6f21bb077c384d54e6%40djangoproject.com.

Reply via email to