Opened 9 years ago
Last modified 9 years ago
#25698 closed Uncategorized
App without migrations depending on app with migrations fails on initial migrate call (postgres) — at Version 2
Reported by: | Lucas Moeskops | Owned by: | nobody |
---|---|---|---|
Component: | Migrations | Version: | 1.8 |
Severity: | Normal | Keywords: | migrate postgres |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description (last modified by )
Simple test example:
In a new project add 'django.contrib.sites' and your main app to the INSTALLED APPS
setting.
Use postgres as database.
Make a model in your main app that uses a relation to django.contrib.sites:
from django.contrib.sites.models import Site class MyModel(models.Model): my_site = models.ForeignKey(Site)
Migrate the project:
python manage.py migrate
It will fail to migrate with the message: django.db.utils.ProgrammingError: relation "django_site" does not exist
. This is because it tries to migrate the apps without migrations before the apps with migrations.
To solve the problem, the app should have at least one migration. But maybe this needs to be documented. I couldn't find it in the documentation.
Change History (2)
comment:1 by , 9 years ago
Description: | modified (diff) |
---|
comment:2 by , 9 years ago
Description: | modified (diff) |
---|