django-migrations

问题 To setup new database on heroku I tried python manage migrate and got many exceptions related to relation already exists/does not exists . So I followed the instructions here django 1.9: ProgrammingError: relation "users_user" does not exist but it didn't work. ~ $ django-admin showmigrations admin [ ] 0001_initial [ ] 0002_logentry_remove_auto_add auth [ ] 0001_initial [ ] 0002_alter_permission_name_max_length [ ] 0003_alter_user_email_max_length [ ] 0004_alter_user_username_opts [ ] 0005

问题 To setup new database on heroku I tried python manage migrate and got many exceptions related to relation already exists/does not exists . So I followed the instructions here django 1.9: ProgrammingError: relation "users_user" does not exist but it didn't work. ~ $ django-admin showmigrations admin [ ] 0001_initial [ ] 0002_logentry_remove_auto_add auth [ ] 0001_initial [ ] 0002_alter_permission_name_max_length [ ] 0003_alter_user_email_max_length [ ] 0004_alter_user_username_opts [ ] 0005

问题 I upgraded from Django 1.7 to Django 1.9. I have a number of migrations. Since the upgrade I can no longer create a fresh database. The problem is that "django manage.py migrate" runs checks. The checks import the application urls. These ultimately import code that looks up the database. I can get the migration to work, by modifying the migrate.py script and adding this line (as per Django: skip system check when running custom command): requires_system_checks = False Is there a standard

问题 what i'm trying to do is to change the default path for migrations for a specific application in a django project to put it outside the project itself but keeping it transparent, keeping use of makemigrations and migrate . Is it possible? if yes, how? 回答1: Django has a MIGRATION_MODULES setting. It allows you to specify a different module for migrations per app. The module can be outside of the Django project, it just needs to be on your python path. MIGRATION_MODULES = {'myapp': 'othermodule

问题 I am using ProjectState to migrate to a new attributes of a table. I am trying to understand the ModelState and ProjectState using of migrations API in Django 3.0.3. I am unable to migrate to the new state which has new fields. Can someone help me with the ProjectState and ModelState usage of what to apply for new model_definition migration to work? The following code does not migrate to DB but doesnt give any error. I want to migrate from a DB table state to another state and there are some

问题 I am using ProjectState to migrate to a new attributes of a table. I am trying to understand the ModelState and ProjectState using of migrations API in Django 3.0.3. I am unable to migrate to the new state which has new fields. Can someone help me with the ProjectState and ModelState usage of what to apply for new model_definition migration to work? The following code does not migrate to DB but doesnt give any error. I want to migrate from a DB table state to another state and there are some

来源： https://stackoverflow.com/questions/40705237/django-db-migrations-exceptions-circulardependencyerror

来源： https://stackoverflow.com/questions/40705237/django-db-migrations-exceptions-circulardependencyerror

来源： https://stackoverflow.com/questions/60254433/error-using-checkconstraint-in-model-meta-along-with-django-genericforeignkey

来源： https://stackoverflow.com/questions/32531350/django-1-8-run-a-specific-migration