makemigrations and migrate commands in Django

Introduction

These commands help you save and apply changes to your database structure easily.

When you add or change a model in your Django app.

When you want to create the initial database tables for your app.

When you want to update the database after changing fields or adding new ones.

When you want to share database changes with your team.

When setting up a new environment and need to create the database schema.

Syntax

Django

python manage.py makemigrations
python manage.py migrate

makemigrations creates files that describe your database changes.

migrate applies those changes to the actual database.

Examples

This command checks your models and prepares migration files for any changes.

Django

python manage.py makemigrations

This command applies all pending migrations to update your database.

Django

python manage.py migrate

This creates migration files only for the specified app.

Django

python manage.py makemigrations appname

This applies migrations up to a specific migration number for an app.

Django

python manage.py migrate appname 0001

Sample Program

This example shows a simple model for books. Running makemigrations creates a migration file describing the new table. Running migrate creates the table in the database.

Django

# models.py
from django.db import models

class Book(models.Model):
    title = models.CharField(max_length=100)
    author = models.CharField(max_length=100)

# Terminal commands
# Step 1: Create migration files
# python manage.py makemigrations

# Step 2: Apply migrations to database
# python manage.py migrate

Important Notes

Always run makemigrations after changing models to keep migrations up to date.

Run migrate to apply all migrations before running your app to avoid errors.

You can look inside migration files to see what changes will be applied.

Summary

makemigrations creates files describing database changes.

migrate applies those changes to the database.

Use these commands to keep your database structure in sync with your Django models.

Practice

1. What is the main purpose of the makemigrations command in Django?

easy

A. To delete old migration files

B. To apply changes to the database

C. To start the Django development server

D. To create migration files that describe changes in models

Solution

1. Step 1: Understand the role of makemigrations

   This command generates files that describe changes made to Django models, like adding or removing fields.

2. Step 2: Differentiate from migrate

   migrate applies those changes to the database, but makemigrations only creates the description files.

3. Final Answer:

   To create migration files that describe changes in models -> Option D

4. Quick Check:

   makemigrations creates files = A [OK]

Hint: Remember: makemigrations creates files, migrate applies them [OK]

Common Mistakes:

• Confusing makemigrations with migrate
• Thinking makemigrations changes the database directly
• Assuming makemigrations starts the server

2. Which of the following is the correct command to apply migrations to the database in Django?

easy

A. python manage.py makemigrations

B. python manage.py migrate

C. python manage.py runserver

D. python manage.py makemigrate

Solution

1. Step 1: Identify the command to apply migrations

   The command python manage.py migrate applies migration files to update the database schema.

2. Step 2: Check other options

   makemigrations creates migration files, runserver starts the server, and makemigrate is not a valid command.

3. Final Answer:

   python manage.py migrate -> Option B

4. Quick Check:

   Apply migrations = migrate = A [OK]

Hint: Use migrate to apply changes, not makemigrations [OK]

Common Mistakes:

• Typing makemigrate instead of migrate
• Using makemigrations to update the database
• Confusing runserver with migration commands

3. Given the following sequence of commands in a Django project:

python manage.py makemigrations
python manage.py migrate

What will happen after running these commands?

medium

A. The database schema will be updated to match the current models

B. The server will start running

C. Migration files will be deleted

D. The models will be reset to default

Solution

1. Step 1: Understand the effect of makemigrations

   This command creates migration files describing model changes.

2. Step 2: Understand the effect of migrate

   This command applies those migration files to update the database schema accordingly.

3. Final Answer:

   The database schema will be updated to match the current models -> Option A

4. Quick Check:

   makemigrations + migrate = update DB schema = C [OK]

Hint: makemigrations then migrate updates database schema [OK]

Common Mistakes:

• Thinking migrate starts the server
• Believing migration files get deleted automatically
• Assuming models reset after migrations

4. You ran python manage.py migrate but got an error saying "No migrations to apply." What is the most likely cause?

medium

A. You forgot to run makemigrations to create migration files

B. The database is corrupted

C. You need to restart the Django server

D. Your models have syntax errors

Solution

1. Step 1: Analyze the error message

   "No migrations to apply" means Django found no new migration files to run.

2. Step 2: Identify the missing step

   If you did not run makemigrations, no migration files exist to apply.

3. Final Answer:

   You forgot to run makemigrations to create migration files -> Option A

4. Quick Check:

   No migrations found = forgot makemigrations = D [OK]

Hint: Run makemigrations before migrate to create migration files [OK]

Common Mistakes:

• Restarting server instead of creating migrations
• Assuming database corruption without checking migrations
• Ignoring missing migration files

5. You added a new field to a Django model but forgot to run makemigrations. Later, you run python manage.py migrate. What will happen?

hard

A. The new field will be added to the database automatically

B. An error will occur because migration files are missing

C. Nothing changes in the database schema

D. Django will create migration files automatically and apply them

Solution

1. Step 1: Understand the role of makemigrations

   This command creates migration files describing model changes like new fields.

2. Step 2: Effect of running migrate without new migration files

   If no migration files exist, migrate finds nothing to apply, so the database stays unchanged.

3. Final Answer:

   Nothing changes in the database schema -> Option C

4. Quick Check:

   No migration files = migrate does nothing = B [OK]

Hint: Always run makemigrations after model changes before migrate [OK]

Common Mistakes:

• Expecting migrate to detect model changes automatically
• Assuming migrate creates migration files
• Thinking database updates without migration files