Bird
Raised Fist0
FastAPIframework~30 mins

Alembic migrations in FastAPI - Mini Project: Build & Apply

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Alembic Migrations with FastAPI
📖 Scenario: You are building a simple FastAPI app to manage books in a library. You want to keep track of your database changes safely using Alembic migrations.
🎯 Goal: Create a basic Alembic migration setup for a FastAPI project. Define an initial database model, configure Alembic, generate a migration script, and apply it to create the database table.
📋 What You'll Learn
Create a SQLAlchemy model for a Book with id and title fields
Set up Alembic configuration with the correct database URL
Generate an Alembic migration script for the Book model
Apply the migration to create the books table in the database
💡 Why This Matters
🌍 Real World
Alembic migrations help developers safely update database schemas as their applications grow and change.
💼 Career
Understanding Alembic migrations is essential for backend developers working with FastAPI and SQLAlchemy to maintain database integrity.
Progress0 / 4 steps
1
Create the SQLAlchemy Book model
Create a SQLAlchemy model class called Book with a table name books. It should have two columns: id as an integer primary key and title as a string of max length 100.
FastAPI
Hint

Use class Book(Base): and set __tablename__ = 'books'. Define id and title columns with correct types.

2
Configure Alembic with the database URL
Add a variable called SQLALCHEMY_DATABASE_URL and set it to sqlite:///./test.db. This will be the database URL Alembic uses.
FastAPI
Hint

Set SQLALCHEMY_DATABASE_URL exactly to "sqlite:///./test.db".

3
Generate Alembic migration script
Write a command string variable called alembic_command with the value "alembic revision --autogenerate -m 'create books table'". This command generates the migration script for the Book model.
FastAPI
Hint

Set alembic_command to the exact Alembic command string to generate migration.

4
Apply Alembic migration to create the table
Write a command string variable called alembic_upgrade with the value "alembic upgrade head". This command applies the migration and creates the books table in the database.
FastAPI
Hint

Set alembic_upgrade to the exact Alembic command string to apply migration.

Practice

(1/5)
1. What is the main purpose of Alembic migrations in a FastAPI project?
easy
A. To manage and apply database schema changes safely over time
B. To handle HTTP requests and responses
C. To serve static files like images and CSS
D. To create user interface components

Solution

  1. Step 1: Understand Alembic's role

    Alembic is a tool designed to manage database schema changes, not web server tasks.
  2. Step 2: Identify the correct purpose

    It helps developers apply, track, and revert database changes safely during development and deployment.
  3. Final Answer:

    To manage and apply database schema changes safely over time -> Option A
  4. Quick Check:

    Alembic = database migrations [OK]
Hint: Alembic is for database schema changes, not web or UI tasks [OK]
Common Mistakes:
  • Confusing Alembic with FastAPI routing
  • Thinking Alembic serves static files
  • Assuming Alembic builds UI components
2. Which Alembic command creates a new migration script file?
easy
A. alembic upgrade head
B. alembic init migrations
C. alembic downgrade -1
D. alembic revision -m "message"

Solution

  1. Step 1: Identify commands for migration scripts

    The command to create a new migration script is revision with a message describing the change.
  2. Step 2: Match the command

    alembic revision -m "message" creates a new migration file with the given message.
  3. Final Answer:

    alembic revision -m "message" -> Option D
  4. Quick Check:

    revision = create migration script [OK]
Hint: Use 'revision' with -m to create migration scripts [OK]
Common Mistakes:
  • Using 'upgrade' to create scripts instead of apply them
  • Confusing 'downgrade' with script creation
  • Using 'init' after project setup
3. Given this Alembic command sequence:
alembic revision -m "add users table"
alembic upgrade head
What happens after running these commands?
medium
A. The database schema is reset to the initial state
B. The migration script is deleted and no changes are applied
C. A new migration script is created and the database schema is updated to include the users table
D. The database schema is downgraded by one version

Solution

  1. Step 1: Understand the revision command

    alembic revision -m "add users table" creates a new migration script file describing the addition of the users table.
  2. Step 2: Understand the upgrade command

    alembic upgrade head applies all migrations up to the latest, updating the database schema accordingly.
  3. Final Answer:

    A new migration script is created and the database schema is updated to include the users table -> Option C
  4. Quick Check:

    revision + upgrade = new migration applied [OK]
Hint: Revision creates script; upgrade applies it to DB [OK]
Common Mistakes:
  • Thinking upgrade resets or deletes migrations
  • Confusing downgrade with upgrade
  • Assuming revision applies changes immediately
4. You run alembic upgrade head but get an error about missing dependencies in your migration script. What is the best way to fix this?
medium
A. Edit the migration script to add missing imports or fix syntax errors
B. Delete all migration scripts and start over
C. Run alembic downgrade base without fixing scripts
D. Ignore the error and rerun the command

Solution

  1. Step 1: Identify cause of error

    Missing dependencies or syntax errors in migration scripts cause upgrade failures.
  2. Step 2: Fix the migration script

    Editing the script to add missing imports or correct syntax resolves the error and allows upgrade to succeed.
  3. Final Answer:

    Edit the migration script to add missing imports or fix syntax errors -> Option A
  4. Quick Check:

    Fix script errors before upgrading [OK]
Hint: Fix migration script errors before upgrading [OK]
Common Mistakes:
  • Deleting scripts unnecessarily
  • Ignoring errors and retrying blindly
  • Downgrading without fixing root cause
5. You want to add a new column to an existing table using Alembic migrations. Which sequence correctly applies this change without losing existing data?
hard
A. Delete the database and recreate it with the new column
B. Create a new revision script adding the column, then run alembic upgrade head
C. Modify the existing migration script that created the table and rerun alembic upgrade head
D. Run alembic downgrade base then create a new revision script

Solution

  1. Step 1: Create a new migration script

    Adding a new column requires a new migration script describing the change to preserve history and data.
  2. Step 2: Apply the migration

    Running alembic upgrade head applies the new migration safely without deleting existing data.
  3. Final Answer:

    Create a new revision script adding the column, then run alembic upgrade head -> Option B
  4. Quick Check:

    New revision + upgrade = safe schema update [OK]
Hint: Always create new revision for schema changes, then upgrade [OK]
Common Mistakes:
  • Modifying old migration scripts after applying
  • Deleting database instead of migrating
  • Downgrading unnecessarily before adding columns