DB migrations and schema changes

Manage Alembic migrations across SQLite and Postgres by setting the LETTA_PG_URI environment variable to switch backends. Use 'just ready' for environment setup and apply version-controlled schema upgrades safely.

Autogenerate Alembic revisions by modifying your ORM models and running the revision command through uv and Alembic. This detects schema changes and creates version-controlled migration scripts automatically.

You need uv and just to run database schema changes for local development. The 'just ready' command uses these tools to orchestrate environment setup and apply Alembic migrations consistently.

You can use Alembic to apply schema upgrades in production-like environments. The workflow supports version-controlled migrations and database upgrades tailored for both local development and production-like deployments.

Alembic migrations may fail when switching database backends if LETTA_PG_URI is not set correctly. Ensure the environment is configured with 'just ready' and the target database URI matches the expected backend.

Version-controlled migration orchestration reduces manual schema errors by automating Alembic revisions, upgrades, and downgrades. This enforces consistent schema changes across SQLite and Postgres environments with minimal risk.