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
24669	"Migrations should only be marked as run on ""their"" db"	Simon Percivall	nobody	"We're using a multi database setup. Each db will have all migrations written to the ""django_migrations"" table, even if the migration doesn't apply to that db. Also, state is calculated for each migration, even when, again, that migration doesn't apply.

It'd (for the writing of migrations to the db) be less confusing and cleaner to write only applicable migrations to ""django_migrations"". And it would be faster if state were to be calculated only when necessary. As it is, building up state for all models takes a considerable amount of time when running migrations on a ""non-default"" database where we only have a few tables."	Cleanup/optimization	new	Migrations	1.7	Normal				Accepted	0	0	0	0	0	0