Migrations concept and workflow in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new migration for your Django app.

Django

python manage.py [1]

Drag options to blanks, or click blank then click option'

Arunserver

Bmakemigrations

Ccreatesuperuser

Dmigrate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'migrate' instead of 'makemigrations' to create migration files.

Running 'runserver' expecting migrations to be created.

Use makemigrations to create new migration files based on model changes.

2fill in blank

medium

Complete the code to apply all pending migrations to the database.

Django

python manage.py [1]

Drag options to blanks, or click blank then click option'

Amigrate

Bshell

Cflush

Dmakemigrations

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'makemigrations' to apply migrations instead of creating them.

Using 'flush' which deletes data instead of applying migrations.

The migrate command applies migrations to update the database schema.

3fill in blank

hard

Fix the error in the migration command to specify the app name.

Django

python manage.py makemigrations [1]

Drag options to blanks, or click blank then click option'

Amyapp

Bmigrate

Call

Drunserver

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'all' or 'migrate' as app names.

Omitting the app name when you want to target a specific app.

Specify your app name (e.g., myapp) to create migrations only for that app.

4fill in blank

hard

Fill both blanks to create a migration that adds a new field to a model.

Django

class Migration(migrations.Migration):
    dependencies = [
        ('[1]', '0001_initial'),
    ]

    operations = [
        migrations.AddField(
            model_name='[2]',
            name='new_field',
            field=models.CharField(max_length=100),
        ),
    ]

Drag options to blanks, or click blank then click option'

Ablog

Bpost

Cuser

Dcomment

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up app name and model name.

Using capitalized model names in model_name.

The dependencies list must include the app name and previous migration. The model_name is the model receiving the new field.

5fill in blank

hard

Fill all three blanks to write a migration that removes a field from a model.

Django

class Migration(migrations.Migration):
    dependencies = [
        ('[1]', '0002_auto_20240101_1234'),
    ]

    operations = [
        migrations.RemoveField(
            model_name='[2]',
            name='[3]',
        ),
    ]

Drag options to blanks, or click blank then click option'

Ashop

Bproduct

Cdescription

Dprice

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong migration dependency name.

Confusing field name with model name.

The dependencies specify the app and migration to depend on. The model_name is the model to change, and name is the field to remove.

Practice

1. What is the main purpose of Django migrations?

easy

A. To keep the database schema synchronized with Django models

B. To create HTML templates automatically

C. To manage user authentication

D. To optimize Django views for speed

Solution

1. Step 1: Understand what migrations do

   Django migrations track changes in models and update the database schema accordingly.

2. Step 2: Compare options with this purpose

   Only To keep the database schema synchronized with Django models describes keeping the database schema in sync with models, which is the core purpose of migrations.

3. Final Answer:

   To keep the database schema synchronized with Django models -> Option A

4. Quick Check:

   Migrations purpose = sync DB schema [OK]

Hint: Migrations sync models and database structure [OK]

Common Mistakes:

• Confusing migrations with template or view management
• Thinking migrations handle user authentication
• Assuming migrations optimize performance

2. Which command do you run to create new migration files after changing models?

easy

A. python manage.py migrate

B. python manage.py makemigrations

C. python manage.py runserver

D. python manage.py collectstatic

Solution

1. Step 1: Identify the command for creating migration files

   The command makemigrations generates migration files based on model changes.

2. Step 2: Differentiate from other commands

   migrate applies migrations, runserver starts the server, and collectstatic collects static files.

3. Final Answer:

   python manage.py makemigrations -> Option B

4. Quick Check:

   Create migrations = makemigrations [OK]

Hint: Use makemigrations to create migration files [OK]

Common Mistakes:

• Using migrate instead of makemigrations to create files
• Confusing runserver with migration commands
• Thinking collectstatic manages migrations

3. Given this sequence of commands:

python manage.py makemigrations
python manage.py migrate

What happens after running these commands?

medium

A. The server starts running with updated models

B. Static files are collected and served

C. Migration files are created and then applied to update the database schema

D. The database is reset to initial state

Solution

1. Step 1: Understand makemigrations effect

   This command creates migration files reflecting model changes but does not apply them yet.

2. Step 2: Understand migrate effect

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

3. Final Answer:

   Migration files are created and then applied to update the database schema -> Option C

4. Quick Check:

   makemigrations + migrate = create & apply migrations [OK]

Hint: makemigrations creates files; migrate applies them [OK]

Common Mistakes:

• Thinking migrate creates migration files
• Assuming these commands start the server
• Confusing static file commands with migrations

4. You ran python manage.py migrate but got an error saying a migration file is missing. What is the likely cause?

medium

A. You forgot to run makemigrations to create migration files

B. You ran migrate before starting the server

C. Your models.py file is empty

D. You need to delete the database before migrating

Solution

1. Step 1: Analyze the error about missing migration files

   This usually means migration files were not created yet for model changes.

2. Step 2: Identify the missing step

   Running makemigrations generates migration files needed before applying them with migrate.

3. Final Answer:

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

4. Quick Check:

   Missing migration files = forgot makemigrations [OK]

Hint: Always run makemigrations before migrate [OK]

Common Mistakes:

• Thinking migrate creates migration files
• Assuming server must run before migrate
• Believing database must be deleted before migrating

5. You added a new field to a model and want to share the changes with your team. What is the correct workflow to update the database and share the changes safely?

hard

A. Delete the database, then run makemigrations and migrate on each machine

B. Run migrate first, then create migration files manually and share them

C. Only update the models.py file and ask team members to restart their servers

D. Run makemigrations, commit migration files to version control, then run migrate on all machines

Solution

1. Step 1: Create migration files after model changes

   Run makemigrations to generate migration files reflecting the new field.

2. Step 2: Share migration files and apply them

   Commit migration files to version control so the team can get them, then run migrate on each machine to update the database schema safely.

3. Final Answer:

   Run makemigrations, commit migration files to version control, then run migrate on all machines -> Option D

4. Quick Check:

   makemigrations + commit + migrate = safe team update [OK]

Hint: Commit migration files before migrating on other machines [OK]

Common Mistakes:

• Running migrate before creating migration files
• Deleting databases unnecessarily
• Only updating models.py without migrations