#28953: makemigrations with specified app label tries to connect to other
databases
that are not directly related
-------------------------------------+-------------------------------------
Reporter: André | Owner: nobody
Glatzl |
Type: Bug | Status: new
Component: | Version: 2.0
Uncategorized | Keywords: makemigrations
Severity: Normal | databases
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
When i run 'makemigrations' with the app label defined, i expect only to
use the database that is linked to this app. Somehow, makemigrations tries
to access databases that are not directly related to the current app. Yes,
the models in the app has relations with other databases, which makes
sense to check if there is something to migrate but this is kind of
irritating because every time, i need to cut of the databases from
settings that i don't want to affect (not used by the app).
Maybe it's not a bug but maybe we could convert this to a feature where
you could use an argument where it ignores indirectly relationships with
databases.
Best regards
--
Ticket URL: <https://code.djangoproject.com/ticket/28953>
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/049.c9e24518abf097327c9727134701926f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
