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
27200	Provide makemigrations router.allow_migrate() with a model_name	Joseph Kahn	nobody	"I maintain a package called https://github.com/JBKahn/django-sharding and I don't really understand what the expected behaviour is when an app calls allow_migrate(db, app_label). What is it asking?

If I've got data on more than one database and Django cannot tell me the name of the model or the instance, then what am I expected to respond with? I made model_name or a hint about the model a hard requirement in the router since you cannot reason about the result without the context of a model. Two models in the same app could be on a different database. Recently, in Django 1.10, this call was added to `makemigrations`. I'm not sure what to return or how to handle this case/force a hint in the event of a runython call but not a makemigrations call.

More so, I'm not sure how one is expected to be able to write a router to handle this?"	Cleanup/optimization	closed	Migrations	1.10	Normal	fixed	makemigrations, router, allow_migrate	Shai Berger	Accepted	1	0	0	0	0	0