Deep Analysis and Solution for Django 1.7 Migration Error: OperationalError no such column

Evolution and Core Mechanisms of Django Migration System

Prior to Django 1.7, database schema management primarily relied on the syncdb command. This command was designed to avoid any operations that might破坏 existing data, meaning when models added new fields, syncdb would not automatically create corresponding columns in the database. Developers needed to either manually drop tables and recreate them or execute SQL statements directly to add columns, both approaches carrying risks of data loss or operational complexity.

The emergence of the third-party library South changed this landscape by introducing a complete database migration framework. South could track model changes, generate migration scripts, and support both forward and backward migrations, significantly improving the convenience and safety of database version management. Django 1.7 integrated South's core functionality into the framework, forming the built-in migration system.

Detailed Workflow of Django 1.7 Migrations

The new migration system adopts a two-step approach: first, use the makemigrations command to detect model changes and generate migration files; then, apply these changes to the database using the migrate command. This design ensures that database schema changes are controllable and traceable.

Here is a complete migration workflow example:

# Detect model changes and generate migration files
python manage.py makemigrations

# Apply migrations to the database
python manage.py migrate

Adding Non-Nullable Fields and Default Value Issues

When adding non-nullable fields to existing models, the migration system faces data integrity challenges. The database requires all existing records to have values for the new field, necessitating the provision of default values.

Consider the following model definition:

from django.db import models

class Snippet(models.Model):
    owner = models.ForeignKey('auth.User', related_name='snippets')
    highlighted = models.TextField()
    # Other field definitions...

Here, the highlighted field is defined as TextField, which by default does not allow null values. When attempting to add this field to a table with existing data, the migration system prompts:

You are trying to add a non-nullable field 'highlighted' to snippet without a default;
we can't do that (the database needs something to populate existing rows).
Please select a fix:
 1) Provide a one-off default now (will be set on all existing rows)
 2) Quit, and let me add a default in models.py

Solutions and Best Practices

For adding non-nullable fields, there are two main solutions:

Solution 1: Define Default Values in the Model

Directly specify default values for fields in the model definition, which is the most recommended approach:

class Snippet(models.Model):
    owner = models.ForeignKey('auth.User', related_name='snippets')
    highlighted = models.TextField(default='')
    # Other field definitions...

This way, the migration system automatically uses an empty string as the default value for existing records.

Solution 2: Provide a One-Off Default During Migration

If you prefer not to modify the model definition, you can choose to provide a one-off default when running makemigrations. The system will prompt for a default value, which is used only in this migration.

For foreign key fields like owner, the situation is more complex. Foreign keys need to reference existing user records. A common solution is:

owner = models.ForeignKey('auth.User', related_name='snippets', null=True)

First, set the field to nullable, and after migration is complete, change it to non-nullable if needed.

Complete Problem Resolution Process

For the specific scenario in the original problem, the complete resolution steps are:

First, ensure the model is correctly defined with default values:

class Snippet(models.Model):
    owner = models.ForeignKey('auth.User', related_name='snippets', null=True)
    highlighted = models.TextField(default='')
    created = models.DateTimeField(auto_now_add=True)
    title = models.CharField(max_length=100, blank=True, default='')
    code = models.TextField()
    linenos = models.BooleanField(default=False)
    language = models.CharField(choices=LANGUAGE_CHOICES, default='python', max_length=100)
    style = models.CharField(choices=STYLE_CHOICES, default='friendly', max_length=100)

Then execute the migration commands:

python manage.py makemigrations
python manage.py migrate

If the database contains important data that needs preservation, consider backing up the data first, then rebuild the database as mentioned in Answer 2: delete the db.sqlite3 file and re-execute the migration commands.

Advanced Features of the Migration System

The Django migration system also offers many advanced features:

Data Migrations: Beyond schema changes, you can write data migration scripts to transform existing data.

Dependency Management: Migration files can declare dependencies to ensure migrations are executed in the correct order.

Rollback Support: Use migrate app_name migration_name to rollback to a specific migration state.

Understanding these features helps in better planning and managing database evolution.