context-database-schema

Alembic migrations manage schema changes incrementally. Navigate to your backend directory, run `poetry run alembic upgrade head` to apply pending migrations, or create new migrations with `poetry run alembic revision -m "description"` before applying them. This workflow ensures consistent schema evolution across environments like Railway Postgres.

Legacy Supabase migrations are deprecated for runtime use and kept only for archival reference. Alembic-based migrations are the current standard for Railway Postgres deployments, providing version control, rollback capability, and reproducible schema changes. Use Alembic for all new migrations.

This error occurs when migrations haven't been applied or a table reference is missing. Verify pending migrations with Alembic status, apply all migrations with `poetry run alembic upgrade head`, and check that table names and schemas match your migration definitions. Manual SQL inspection may be needed to diagnose schema state.

Yes. RLS policies are part of the schema management scope in this Skill. Define and apply RLS policies through migrations or manual SQL to enforce access control on Supabase and Railway Postgres tables, coordinating with your migration workflow.

Type generation tooling converts your database schema into TypeScript or language-specific type definitions. Reference the Skill's type generation documentation and tooling references to automate type creation from your 86+ migrations, reducing manual type maintenance.

Ensure your backend environment is configured with Poetry, Alembic is initialized, your database connection is set in environment variables, and all migration files are committed. Verify Railway Postgres connectivity before running `poetry run alembic upgrade head` to apply schema changes.