id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
27110	makemigrations shouldn't create `django_migrations` table in external databases	direx	Tim Graham	"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."	Bug	closed	Migrations	1.10	Release blocker	fixed	regression		Accepted	1	0	0	0	0	0