Creating tables (db.create_all) in Flask - Visual Walkthrough

Concept Flow - Creating tables (db.create_all)

Define Models

↓

Initialize Flask App

↓

Configure Database URI

↓

Create SQLAlchemy db Object

↓

Call db.create_all()

↓

Tables Created in Database

↓

App Ready to Use Database

This flow shows how Flask app models are defined, then db.create_all() creates corresponding tables in the database.

Execution Sample

Flask

from flask import Flask
from flask_sqlalchemy import SQLAlchemy
app = Flask(__name__)
app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///test.db'
db = SQLAlchemy(app)

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    name = db.Column(db.String(50))

with app.app_context():
    db.create_all()

This code defines a User model and creates its table in the SQLite database using db.create_all().

Execution Table

Step	Action	Evaluation	Result
1	Define User model	User inherits db.Model with id and name columns	Model ready for table creation
2	Initialize Flask app	app created	App object ready
3	Set database URI	URI set to sqlite:///test.db	Config ready for DB connection
4	Create SQLAlchemy db object	db linked to app	db object ready to manage models
5	Enter app context	app.app_context() active	Context allows DB operations
6	Call db.create_all()	Checks models and creates tables if missing	User table created in test.db
7	Exit app context	Context closed	App ready to use database tables

💡 All defined models have corresponding tables created in the database.

Variable Tracker

Variable	Start	After Step 1	After Step 4	After Step 6	Final
app	None	None	Flask app instance	Flask app instance	Flask app instance
db	None	None	SQLAlchemy instance linked to app	SQLAlchemy instance linked to app	SQLAlchemy instance linked to app
User	None	Model class defined	Model class defined	Model class defined	Model class defined
Database Tables	Empty	Empty	Empty	User table created	User table created

Key Moments - 2 Insights

Why do we need to call db.create_all() inside app.app_context()?

Because Flask needs an active app context to know which app and database to use. Without it, db.create_all() cannot access the app configuration (see execution_table step 5 and 6).

Does db.create_all() delete existing tables before creating new ones?

No, db.create_all() only creates tables that do not exist. It does not delete or modify existing tables (see execution_table step 6).

Visual Quiz - 3 Questions

Look at the execution table, what is the state of the database tables after step 4?

A No tables created yet

B User table created

C All tables deleted

D Tables partially created

💡 Hint

Check the 'Database Tables' variable in variable_tracker after step 4.

At which step does the User table get created in the database?

A Step 3

B Step 5

C Step 6

D Step 7

💡 Hint

Look at the 'Action' and 'Result' columns in execution_table for when db.create_all() is called.

If we forget to enter app.app_context(), what will happen when calling db.create_all()?

A Tables will still be created

B An error will occur due to missing app context

C Tables will be deleted

D Nothing happens, silently fails

💡 Hint

Refer to key_moments about the importance of app context for db.create_all().

Concept Snapshot

Define your models as classes inheriting db.Model.
Initialize Flask app and configure database URI.
Create SQLAlchemy db object linked to app.
Use app.app_context() to activate context.
Call db.create_all() to create tables for all models.
Existing tables are not deleted or modified.

Full Transcript

In Flask, to create database tables, you first define your models as Python classes inheriting from db.Model. Then you initialize your Flask app and set the database URI in the app configuration. Next, you create a SQLAlchemy db object linked to your app. To perform database operations like creating tables, you must enter the app context using app.app_context(). Inside this context, calling db.create_all() will create tables in the database for all models that do not already have tables. This process does not delete or modify existing tables. After this, your app is ready to use the database tables.

Practice

1. What does the db.create_all() function do in a Flask application?

easy

A. It updates existing tables to match model changes automatically.

B. It deletes all tables from the database.

C. It creates all tables defined by your models in the database if they don't exist.

D. It runs all database queries defined in your app.

Solution

1. Step 1: Understand the purpose of db.create_all()

   This function creates tables in the database based on your model definitions if those tables do not already exist.

2. Step 2: Recognize what it does not do

   It does not delete tables, update existing tables, or run queries; it only creates missing tables.

3. Final Answer:

   It creates all tables defined by your models in the database if they don't exist. -> Option C

4. Quick Check:

   db.create_all() creates missing tables [OK]

Hint: Remember: create_all only adds missing tables, no updates [OK]

Common Mistakes:

• Thinking it updates existing tables automatically
• Confusing it with deleting tables
• Assuming it runs queries or migrations

2. Which of the following is the correct way to use db.create_all() in a Flask app?

easy

A. Call db.create_all() inside the Flask app context.

B. Call db.create_all() after closing the app.

C. Call db.create_all() before defining your models.

D. Call db.create_all() outside the Flask app context.

Solution

1. Step 1: Understand Flask app context requirement

   Database operations like db.create_all() must run inside the Flask app context to access configuration and database connections properly.

2. Step 2: Identify correct usage

   Calling db.create_all() inside the app context ensures tables are created without errors.

3. Final Answer:

   Call db.create_all() inside the Flask app context. -> Option A

4. Quick Check:

   db.create_all() requires app context [OK]

Hint: Always run db.create_all() inside app context [OK]

Common Mistakes:

• Calling create_all outside app context causing errors
• Calling create_all before models are defined
• Calling create_all after app is closed

3. Given this Flask code snippet, what will happen when db.create_all() is called?

from flask import Flask
from flask_sqlalchemy import SQLAlchemy

app = Flask(__name__)
app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///test.db'
db = SQLAlchemy(app)

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    name = db.Column(db.String(50))

with app.app_context():
    db.create_all()

medium

A. An error will occur because the app context is missing.

B. A new table named 'user' will be created in the database if it doesn't exist.

C. The existing 'user' table will be dropped and recreated.

D. Nothing happens because create_all does not create tables.

Solution

1. Step 1: Check app context usage

   The code calls db.create_all() inside app.app_context(), so the context is correct.

2. Step 2: Understand create_all behavior

   It creates missing tables based on models. Since 'User' model exists, a 'user' table will be created if not present.

3. Final Answer:

   A new table named 'user' will be created in the database if it doesn't exist. -> Option B

4. Quick Check:

   create_all creates missing tables inside app context [OK]

Hint: create_all adds missing tables, does not drop existing [OK]

Common Mistakes:

• Thinking create_all drops tables
• Forgetting app context causes errors
• Assuming create_all does nothing

4. You run db.create_all() but your new model's table is not created. What is the most likely cause?

medium

A. All of the above.

B. You defined the model after calling db.create_all().

C. The database URI is incorrect or missing.

D. You forgot to run db.create_all() inside the Flask app context.

Solution

1. Step 1: Check app context usage

   Running db.create_all() outside app context causes tables not to be created.

2. Step 2: Check model definition timing and database URI

   If models are defined after calling db.create_all(), their tables won't be created. Also, an incorrect or missing database URI prevents connection.

3. Final Answer:

   All of the above. -> Option A

4. Quick Check:

   App context, model timing, and URI all affect create_all success [OK]

Hint: Check app context, model order, and DB URI if tables missing [OK]

Common Mistakes:

• Ignoring app context errors
• Calling create_all before defining models
• Not setting database URI correctly

5. You want to add a new column to an existing table after calling db.create_all(). What will happen if you call db.create_all() again without migrations?

hard

A. An error will occur because the table schema changed.

B. The new column will be added automatically to the existing table.

C. The existing table will be dropped and recreated with the new column.

D. Nothing changes; db.create_all() does not modify existing tables.

Solution

1. Step 1: Understand create_all limitations

   db.create_all() only creates missing tables; it does not alter existing tables or add columns.

2. Step 2: Recognize need for migrations

   To change existing tables (like adding columns), you must use migration tools such as Flask-Migrate.

3. Final Answer:

   Nothing changes; db.create_all() does not modify existing tables. -> Option D

4. Quick Check:

   create_all creates tables but does not alter existing ones [OK]

Hint: Use migrations to change tables; create_all only adds missing tables [OK]

Common Mistakes:

• Expecting create_all to update tables
• Not using migration tools for schema changes
• Assuming create_all drops and recreates tables