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
24850	Squashed migration not recognized as an initial migration	Piotr Maliński	nobody	"I have constant problems with squash migrations not being recognised as initial migrations. 

- when '''replaces''' and old migrations exist it's ok
- when '''replaces''' exist and old migrations do not it's ok if there are not dependant migrations in other apps (or NodeNotFoundError will be thrown)
- when both do not exist it tries to execute the migration which fails on an existing database as tables exist

Running migrations with --fake is a local solution, but definitely not optimal for deployment where other migrations may show up and so on. In only one simple example I managed to get migration auto-faked, recognised as initial. In every other it tries to apply it.

I would say that a squash should have an explicit flag that would affect data in django_migrations. Some sort of get_or_create with an entry for that squashed migration so that no matter where the code will go - the table will be updated without the need of any forced --fake operations."	New feature	closed	Migrations	1.8	Normal	duplicate			Unreviewed	0	0	0	0	0	0