如何解决Git回滚后执行Django makemigrations命令出现的'NoneType'对象无'is_relation'属性错误

Hey, I’ve run into this exact headache before after messing with Git rollbacks—super frustrating when the app still runs but you can’t generate new migrations. Let’s break down what’s going on and how to fix it:

What’s Causing This? #

This error pops up when Django’s migration loader tries to process a migration file that references a None value instead of a valid field object. Usually, this happens because:

• A migration file got corrupted during your Git rollback (e.g., parts of the field definition were overwritten or deleted)
• Your local migration files are out of sync with the django_migrations table in your database
• A migration operation (like AlterField or RemoveField) is trying to reference a field that no longer exists in your models.py

Step-by-Step Fixes #

1. Inspect Recent/Corrupted Migration Files

First, check the migration files affected by your Git rollback. Look for any operations where a field is set to None or references a field name not present in your current model. For example, you might see something like this in a broken migration:

operations = [
    migrations.AlterField(
        model_name='post',
        name='content',
        field=None,  # This is the problem—should be a valid type like models.TextField()
    ),
]

If you find this, correct the field definition to match your models.py, or delete the migration entirely if it’s redundant (only do this if the migration wasn’t applied to the database!).

2. Sync Migration Records with Local Files

Run python manage.py showmigrations to see which migrations Django thinks are applied. Compare this with the actual migration files in your app’s migrations/ folder:

• If there are migrations listed as applied that don’t exist locally, delete those entries from the django_migrations table (use your database shell for this).
• If there are local migrations not listed as applied, double-check if they’re safe to apply, or if they’re leftover from the rollback and should be deleted.

3. Reset Migrations (For Severe Cases)

If the migration state is completely messed up, reset migrations for the problematic app (back up your database first!):

• Delete all migration files in the app’s migrations/ folder except __init__.py.
• Use your database shell to delete all entries for the app from django_migrations:

  DELETE FROM django_migrations WHERE app = 'your_app_name';
  

• Regenerate the initial migration: python manage.py makemigrations your_app_name
• Fake-apply the initial migration to avoid altering existing data: python manage.py migrate --fake-initial your_app_name

4. Validate Your Model Files

Double-check your models.py for syntax errors or missing field definitions. A typo (like forgetting to define a field’s type) can cause Django to interpret a field as None during migration processing.

Important Note #

Always back up your database before making changes to migration records or files—you don’t want to accidentally lose data!

内容的提问来源于stack exchange，提问作者Elijah Samuels