Opened 8 years ago
Closed 8 years ago
#27177 closed Bug (worksforme)
Migrations not found for app with same name as project
| Reported by: | Paul Haesler | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.10 |
| Severity: | Normal | Keywords: | migrations project app |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
django_admin creates a project subdirectory that has the same name as the project directory and is NOT an app. However, there is nothing stopping you from creating a models.py file, migrations subdirectory, view.py, etc and adding to INSTALLED_APPS - and I can't find anything in the documentation suggesting that you should not do this.
Indeed this worked fine in 1.9. But having upgraded to 1.10, the commands "makemigration", "migrate", "showmigrations", etc. no longer detect migrations in this project app: Makemigrations doesn't pick up changes to models in that app; showmigrations will not list any migrations from that app; and migrate will not run migrations from that app.
Either this is a bug, or the documentation should state that upgrading the project subdirectory to an app is not supported.
Actually scratch this ticket. The problem was due to a circular dependency in a migration. (A migration that declared that it "replaced" itself.) The real question is why it used to work in 1.9!