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>
I got the same problem (column not exist) but when I try to run migrate not with makemigrations (it is the same issue I believe) Cause: I removed the migration files and replaced them with single pretending intial migration file 0001 before running the migration for the last change Solution: Drop tables involved in that … Read more
I just learned how to do this with a single migration! When running makemigrations django should ask you to set a one-off default. Define whatever you can here to keep it happy, and you’ll end up with the migration AddField you mentioned. migrations.AddField( model_name=”series”, name=”updated_as”, field=models.DateTimeField(default=????, auto_now=True), preserve_default=False, ), Change this one operation into 3 … Read more
Django 2.2 and later As of version 2.2 Django supports declarative partial unique indexes on databases that support them (PostgreSQL and SQLite). So you could do something like: from django.db.models import Model, Q, UniqueConstraint class Post(Model): … class Meta: constraints = [ UniqueConstraint( fields=[“title”, “blog”, “category”], name=”idx1″, condition=Q(category__isnull=False)), UniqueConstraint( fields=[“title”, “blog”], name=”idx2″, condition=Q(category__isnull=True)), ] Django … Read more
Another reason for this maybe because you try to set a column to NOT NULL when it actually already has NULL values.
Here is an example doing everything in one single migration thanks to a RunPython call. # -*- coding: utf-8 -* from __future__ import unicode_literals from django.db import migrations, models import uuid def create_uuid(apps, schema_editor): Device = apps.get_model(‘device_app’, ‘Device’) for device in Device.objects.all(): device.uuid = uuid.uuid4() device.save() class Migration(migrations.Migration): dependencies = [ (‘device_app’, ‘XXXX’), ] operations … Read more
Look at this workaround, posted by Bernie Sumption to the Django developers mailing list: If makemigrations has not yet been run, the “migrate” command treats an app as unmigrated, and creates tables directly from the models just like syncdb did in 1.6. I defined a new settings module just for unit tests called “settings_test.py”, which … Read more
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
Finally got it to work, although I don’t know why and I hope it will work in the future. After doing numerous trials and going through Django’s dev site (link). Here are the steps (for whoever runs into this problem): Empty the django_migrations table: delete from django_migrations; For every app, delete its migrations folder: rm … Read more
To create initial migrations for an app, run makemigrations and specify the app name. The migrations folder will be created. ./manage.py makemigrations <myapp> Your app must be included in INSTALLED_APPS first (inside settings.py).