[Django] #28481: migrate --fake produces stale content type warning when CreateModel exists in non-initial migration

[Django]

#28481: migrate --fake produces stale content type warning when CreateModel exists
in non-initial migration
--------------------------------------+------------------------
Reporter: Amanda Ng | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+------------------------
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"

--
Ticket URL: <https://code.djangoproject.com/ticket/28481>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#28481: migrate --fake produces stale content type warning when CreateModel exists
in non-initial migration

----------------------------+--------------------------------------

Reporter: Amanda Ng | Owner: nobody

Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Normal | Resolution: fixed

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

----------------------------+--------------------------------------
Changes (by Tim Graham):

* status: new => closed
* resolution: => fixed

Comment:

I guess this is fixed in Django 1.11 because (quoting the 1.11 release
notes) "The prompt for stale content type deletion no longer occurs after
running the `migrate` command. Use the new `remove_stale_contenttypes`
command instead." (#24865)

--
Ticket URL: <https://code.djangoproject.com/ticket/28481#comment:1>