Django 1.7 upgrade error: AppRegistryNotReady: Apps aren’t loaded yet
see http://django.readthedocs.org/en/latest/releases/1.7.html#standalone-scripts import django django.setup()
django-1.7
How to resolve “django.core.exceptions.ImproperlyConfigured: Application labels aren’t unique, duplicates: foo” in Django 1.7?
The problem is that with the changes to apps in Django 1.7, apps are required to have a unique label. By default the app label is the package name, so if you’ve got a package with the same name as one of your app modules (foo in this case), you’ll hit this error. The solution … Read more
django 1.7 migrate gets error “table already exists”
If you have the table created in the database, you can run python manage.py migrate –fake <appname> Mark migrations as run without actually running them Or if you want to avoid some actions in your migration, you can edit the migration file under the app/migrations directory and comment the operations you don’t want to do … Read more
How to simplify migrations in Django 1.7?
I got this. I just figured this out and it is good. First, to clear migrations table: ./manage.py migrate –fake <app-name> zero Remove app-name/migrations/ folder or contents. Make the migrations: ./manage.py makemigrations <app-name> Finally tidy up your migrations without making other database changes: ./manage.py migrate –fake <app-name>
How to migrate back from initial migration in Django 1.7?
You can do the same with Django 1.7+ also: python manage.py migrate <app> zero This clears <app> from migration history and drops all tables of <app> See django docs for more info.
Django 1.7 – makemigrations not detecting changes
If you’re changing over from an existing app you made in django 1.6, then you need to do one pre-step (as I found out) listed in the documentation: python manage.py makemigrations your_app_label The documentation does not make it obvious that you need to add the app label to the command, as the first thing it … Read more