Database migrations with Flask-Migrate - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of Flask-Migrate?

Flask-Migrate is a tool used in Flask applications. What does it mainly help developers do?

A Automatically generate HTML forms for database models

B Manage database schema changes over time using migrations

C Handle user authentication and authorization

D Serve static files like images and CSS

💡 Hint

Think about how your database structure changes as your app grows.

Flask-Migrate helps developers apply and track changes to the database schema safely using migration scripts.

❓ component_behavior

intermediate

What happens when you run 'flask db migrate'?

In a Flask app using Flask-Migrate, what does the command 'flask db migrate' do?

A Creates a new migration script by comparing models to the current database schema

B Applies all pending migrations to the database

C Deletes all migration scripts

D Rolls back the last applied migration

💡 Hint

This command prepares changes but does not apply them yet.

'flask db migrate' generates a migration script reflecting model changes but does not update the database.

📝 Syntax

advanced

Identify the correct way to initialize Flask-Migrate

Given a Flask app and SQLAlchemy db instance, which code correctly initializes Flask-Migrate?

Flask

from flask import Flask
from flask_sqlalchemy import SQLAlchemy
from flask_migrate import Migrate

app = Flask(__name__)
db = SQLAlchemy(app)

# Which line correctly initializes Migrate?

A migrate = Migrate(app, db)

B migrate = Migrate(db, app)

C migrate = Migrate(app)

D migrate = Migrate(db)

💡 Hint

Check the order of arguments in the Migrate constructor.

Flask-Migrate requires the Flask app first, then the database instance to initialize properly.

❓ state_output

advanced

What is the state of the database after 'flask db upgrade'?

After running 'flask db upgrade' in a Flask app using Flask-Migrate, what is true about the database?

A The database schema is rolled back to the previous migration

B The database schema is reset to the initial empty state

C No changes are applied to the database schema

D The database schema matches the latest migration scripts

💡 Hint

This command applies all migrations that have not been applied yet.

'flask db upgrade' applies all pending migrations so the database schema is up to date.

🔧 Debug

expert

Why does 'flask db migrate' fail with 'Target database is not up to date'?

You run 'flask db migrate' but get an error: 'Target database is not up to date'. What is the most likely cause?

A The Flask app is missing the SQLAlchemy db instance

B The migration folder is missing

C There are unapplied migrations; you must run 'flask db upgrade' first

D The database URI is incorrect in the Flask config

💡 Hint

Think about the order of applying migrations before creating new ones.

Flask-Migrate requires the database to be at the latest migration before creating new migration scripts.

Practice

1. What is the main purpose of Flask-Migrate in a Flask application?

easy

A. To handle user authentication and sessions

B. To create HTML templates for the Flask app

C. To manage database schema changes safely using migrations

D. To serve static files like CSS and JavaScript

Solution

1. Step 1: Understand Flask-Migrate's role

   Flask-Migrate is a tool that helps manage changes to the database structure over time.

2. Step 2: Identify the correct purpose

   It uses migrations to safely update the database schema without losing data.

3. Final Answer:

   To manage database schema changes safely using migrations -> Option C

4. Quick Check:

   Flask-Migrate = database migrations [OK]

Hint: Flask-Migrate is about database schema changes [OK]

Common Mistakes:

• Confusing Flask-Migrate with template or static file handling
• Thinking it manages user sessions
• Assuming it creates HTML or CSS files

2. Which command correctly initializes Flask-Migrate in your Flask project?

easy

A. flask db init

B. flask migrate start

C. flask db create

D. flask migrate init

Solution

1. Step 1: Recall the initialization command

   The command to set up Flask-Migrate for the first time is flask db init.

2. Step 2: Check other options

   Other commands like flask migrate start or flask db create are incorrect or do not exist.

3. Final Answer:

   flask db init -> Option A

4. Quick Check:

   Initialize Flask-Migrate = flask db init [OK]

Hint: Use 'flask db init' to start migrations [OK]

Common Mistakes:

• Using 'flask migrate init' instead of 'flask db init'
• Confusing 'start' with 'init'
• Trying commands that don't exist in Flask-Migrate

3. Given the following commands run in order:

flask db init
flask db migrate -m "Add users table"
flask db upgrade

What is the effect on the database?

medium

A. No changes happen until the app restarts

B. The database is reset and all data is lost

C. Only a migration script is created but not applied

D. The database schema is updated with the new users table

Solution

1. Step 1: Understand each command's role

   flask db init sets up migration files, flask db migrate creates a migration script, and flask db upgrade applies changes to the database.

2. Step 2: Determine the final effect

   After running all three, the database schema is updated with the new users table as described in the migration.

3. Final Answer:

   The database schema is updated with the new users table -> Option D

4. Quick Check:

   Upgrade applies migration = schema updated [OK]

Hint: Upgrade applies migration changes to DB [OK]

Common Mistakes:

• Thinking upgrade resets the database
• Believing migrate alone applies changes
• Assuming changes need app restart

4. You run flask db migrate but see no new migration script created. What is the most likely cause?

medium

A. You forgot to run flask db init first

B. No changes detected in the models since last migration

C. The database server is down

D. You need to restart the Flask app

Solution

1. Step 1: Understand what triggers migration scripts

   flask db migrate creates a script only if it detects changes in the database models.

2. Step 2: Identify the cause of no new script

   If no changes are found, no new migration script is generated, which is the most common reason.

3. Final Answer:

   No changes detected in the models since last migration -> Option B

4. Quick Check:

   No model changes = no migration script [OK]

Hint: No model changes means no migration script [OK]

Common Mistakes:

• Assuming database server status affects migration script creation
• Thinking app restart is needed for migrations
• Forgetting to initialize migrations (less common if already done)

5. You want to rename a column in your database using Flask-Migrate. Which sequence of steps is correct?

hard

A. Update the model's column name, run flask db migrate, then flask db upgrade

B. Run flask db upgrade first, then update the model, then flask db migrate

C. Delete the old column manually, update the model, then run flask db migrate

D. Update the model, restart Flask app, then run flask db upgrade

Solution

1. Step 1: Change the model to reflect the new column name

   Modify your SQLAlchemy model to rename the column as desired.

2. Step 2: Create and apply migration

   Run flask db migrate to generate the migration script, then flask db upgrade to apply it to the database.

3. Final Answer:

   Update the model's column name, run flask db migrate, then flask db upgrade -> Option A

4. Quick Check:

   Model change + migrate + upgrade = rename column [OK]

Hint: Change model first, then migrate and upgrade [OK]

Common Mistakes:

• Running upgrade before migrate
• Manually deleting columns instead of migrating
• Restarting app without migration commands