Creating tables (db.create_all) in Flask - Quick Revision & Summary

Recall & Review

beginner

What does db.create_all() do in Flask-SQLAlchemy?

db.create_all() creates all the tables defined by your models in the connected database. It sets up the database structure based on your Python classes.

beginner

When should you call db.create_all() in a Flask app?

You call db.create_all() after defining your models and before running your app, usually once to set up the database tables.

intermediate

Does db.create_all() update existing tables if the model changes?

No, db.create_all() only creates tables if they don't exist. It does not modify existing tables. For updates, you need migrations.

beginner

What is a simple example of using db.create_all() in a Flask app?

<pre>from flask import Flask
from flask_sqlalchemy import SQLAlchemy

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

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

with app.app_context():
    db.create_all()</pre>

intermediate

Why do you need app.app_context() when calling db.create_all()?

Flask needs an application context to know which app and database to use. app.app_context() activates this context so db.create_all() works properly.

What does db.create_all() do in Flask-SQLAlchemy?

A Creates all tables defined by models if they don't exist

B Deletes all tables in the database

C Updates existing tables to match models

D Runs database migrations automatically

db.create_all() creates tables only if they don't exist. It does not delete or update tables.

Which of these is required before calling db.create_all()?

A A migration script

B A running web server

C A database backup

D An active Flask application context

You must have an active Flask app context so Flask knows which app and database to use.

If you change a model after calling db.create_all(), what happens when you call it again?

A Tables are updated automatically

B No changes happen to existing tables

C Old tables are deleted and recreated

D An error is thrown

db.create_all() does not update existing tables. You need migrations for that.

Which database URI is used in this example: sqlite:///mydb.sqlite?

A A local SQLite file database

B A remote MySQL server

C An in-memory PostgreSQL database

D A cloud MongoDB database

This URI points to a local SQLite file named mydb.sqlite.

What is the main limitation of db.create_all()?

A It requires manual SQL commands

B It only works with MySQL

C It cannot modify existing tables

D It deletes all data when run

db.create_all() only creates missing tables; it does not alter existing ones.

Explain how db.create_all() works and when you should use it in a Flask app.

Think about setting up your database structure before running your app.

Describe why db.create_all() is not enough to update your database schema after model changes.

Consider what happens when your app grows and models change.

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