﻿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
28482	migrate --fake produces stale content type warning when CreateModel exists in non-initial migration	Amanda Ng	nobody	"When a new table creation is specified in a subsequent (i.e. non 0001_initial.py) migration, and python manage.py migrate --fake is run, it prompts for deletion of the table as a ""stale content type"".

Steps to reproduce:
1. Create new project. 
2. Create new app.
3. Create a table (e.g. class table1(models.Model)...) in app.
4. Run ""python manage.py makemigrations""
5. Run ""python manage.py migrate""
6. Create a new table in app (e.g. class table2(models.Model)...) in app.
7. Add foreign key to table 1 in table 2.
8. Run ""python manage.py makemigrations""
9. Run ""python manage.py migrate""
10. Delete 0002_* entry from django_migrations table
11. Run ""python manage.py migrate --fake"""	Bug	closed	Migrations	1.10	Normal	duplicate	migrate fake stale		Unreviewed	0	0	0	0	0	0
