#27110: [regression] makemigrations creates `django_migrations` table in
external
databases
-------------------------------+------------------------
Reporter: direx | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Keywords: regression
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------
In Django 1.10 the `makemigrations` command creates a database table
`django_migrations` in '''all databases''' defined in
`settings.DATABASES`. In Django 1.9 and earlier this was not the case.
This behavior is bad if no (or only unmanaged) models reside in these
databases. In my case I have quite a lot of databases defined in
`settings.DATABASES` to be able to connect to them in a unified way. I
only do raw SQL in there, so Django should not mess with these databases
(or worse, introduce schema changes in third-party databases, like Django
1.10 does).
This is somewhat related to Bug #27054, although the fix provided there
does not solve the issue. This regression is introduced by
02ae5fd31a56ffb42feadb49c1f3870ba0a24869.
--
Ticket URL: <https://code.djangoproject.com/ticket/27110>
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/048.105583ab12c86d2cb125bbd70425831f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
