Fix OperationalError: (sqlite3.OperationalError) no such table: user in Flask

This error means SQLAlchemy cannot find the expected database table. It typically happens when you forgot to run migrations, the database file was deleted, or the model was defined after the tables were created. Fix it by running flask db upgrade or creating tables with db.create_all() inside the app context.

Reading the Stack Trace

Here's what each line means:

• File "/app/app/routes.py", line 15, in get_users: The route handler queries the User model, which triggers the SQL statement against a table that does not exist.
• File "/app/venv/lib/python3.12/site-packages/sqlalchemy/engine/cursor.py", line 1348, in _exec_single_context: SQLAlchemy's cursor execution layer attempts to run the SQL but the underlying database engine returns an error.
• sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table: user: The SQLite driver confirms the 'user' table does not exist in the database file.

Common Causes

# Terminal: flask run
# (never ran: flask db upgrade)

from app import db
db.create_all()  # no app context, tables not created

# config.py
SQLALCHEMY_DATABASE_URI = 'sqlite:///prod.db'
# but migrations were run against dev.db

The Fix

Wrap db.create_all() in an app context so SQLAlchemy knows which database to target. For production apps, prefer running flask db upgrade with Alembic migrations instead of create_all().

from app import db
db.create_all()  # called outside app context

from app import create_app, db

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

Testing the Fix

import pytest
from app import create_app, db
from app.models import User

@pytest.fixture
def app():
    app = create_app()
    app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///:memory:'
    app.config['TESTING'] = True
    with app.app_context():
        db.create_all()
        yield app
        db.drop_all()

def test_user_table_exists(app):
    with app.app_context():
        users = User.query.all()
        assert isinstance(users, list)

def test_can_insert_user(app):
    with app.app_context():
        user = User(email='test@example.com')
        db.session.add(user)
        db.session.commit()
        assert User.query.count() == 1

Run your tests:

pytest tests/ -v

Pushing Through CI/CD

git checkout -b fix/flask-sqlalchemy-create-tables,git add app/__init__.py migrations/,git commit -m "fix: run db.create_all inside app context and add migration",git push origin fix/flask-sqlalchemy-create-tables

Your CI config should look something like this:

name: CI
on:
  pull_request:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: '3.12'
          cache: 'pip'
      - run: pip install -r requirements.txt
      - run: pytest tests/ -v --tb=short
      - run: flake8 app/

The Full Manual Process: 18 Steps

Here's every step you just went through to fix this one bug:

1. Notice the error alert or see it in your monitoring tool
2. Open the error dashboard and read the stack trace
3. Identify the file and line number from the stack trace
4. Open your IDE and navigate to the file
5. Read the surrounding code to understand context
6. Reproduce the error locally
7. Identify the root cause
8. Write the fix
9. Run the test suite locally
10. Fix any failing tests
11. Write new tests covering the edge case
12. Run the full test suite again
13. Create a new git branch
14. Commit and push your changes
15. Open a pull request
16. Wait for code review
17. Merge and deploy to production
18. Monitor production to confirm the error is resolved

Total time: 30-60 minutes. For one bug.

pip install bugstack

import bugstack

bugstack.init(api_key=os.environ["BUGSTACK_API_KEY"])

Deploying the Fix (Manual Path)

1. Run pytest locally with an in-memory SQLite database to confirm tables are created.
2. Open a pull request with the migration and context fix.
3. Wait for CI checks to pass on the PR.
4. Have a teammate review and approve the PR.
5. Merge to main and run flask db upgrade in staging before promoting to production.

Frequently Asked Questions