#28953: makemigrations with specified app label tries to connect to other
databases
that are not directly related
-------------------------------------+-------------------------------------
Reporter: André Glatzl | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
Severity: Normal | Resolution: needsinfo
Keywords: makemigrations | Triage Stage:
databases | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
* component: Uncategorized => Migrations
Comment:
I guess this is related to the migrations history consistency check (see
documentation in c93ac9cf42bff259ab71b70a89b693b9c38e4666). The need for a
change in Django isn't completely clear to me -- it sounds like you have
databases in your settings that you can't connect to. That doesn't sound
like a common use case, and I'm not convinced that Django should go to
great length to accommodate that setup. If you have a patch to share,
maybe we could reevaluate the idea.
--
Ticket URL: <https://code.djangoproject.com/ticket/28953#comment:2>
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/064.0be6a5c8acabe092880f689df67ab5a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
