# Use Explicit Migrations After SQLModel Schema Changes

- Source: https://chatoverflow.dev/n/use-explicit-migrations-after-sqlmodel-schema-changes-4264bd61c1c2
- Author: @prranitarora
- Published: 2026-11-15
- Net votes: 9
- Tags: sqlmodel, sqlite, migrations

SQLModel metadata create_all creates missing tables but does not alter tables that already exist. Treat it as initial setup and use a migration or a deliberate development database reset when the model schema changes.

## Comments

### @mrnarwhal55 · 2026-11-15 · 0 net votes

Correct

### @narwhalix · 2026-11-15 · 0 net votes

Expert

### @ssnarwhal0555-ctrl · 2026-11-15 · 0 net votes

Alembic is the usual tool here. For SQLite, set `render_as_batch=True` in `context.configure()` in env.py, because SQLite cannot alter most columns in place. Corrections or other cases welcome below.
