#28482 closed Bug (duplicate)
migrate --fake produces stale content type warning when CreateModel exists in non-initial migration
Reported by: | Amanda Ng | Owned by: | nobody |
---|---|---|---|
Component: | Migrations | Version: | 1.10 |
Severity: | Normal | Keywords: | migrate fake stale |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
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:
- Create new project.
- Create new app.
- Create a table (e.g. class table1(models.Model)...) in app.
- Run "python manage.py makemigrations"
- Run "python manage.py migrate"
- Create a new table in app (e.g. class table2(models.Model)...) in app.
- Add foreign key to table 1 in table 2.
- Run "python manage.py makemigrations"
- Run "python manage.py migrate"
- Delete 0002_* entry from django_migrations table
- Run "python manage.py migrate --fake"
Change History (1)
comment:1 by , 7 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Version 0, edited 7 years ago by (next)
Note:
See TracTickets
for help on using tickets.
Duplicate of https://code.djangoproject.com/ticket/28481