veta-db-migrations

Apply Supabase database migrations safely by enforcing a local-only workflow using Supabase CLI commands for db:push and db:reset. This prevents accidental production impact by restricting schema changes to your local environment before deployment.

To add a new table and enable RLS in a Supabase migration, create a timestamped SQL file in the supabase/migrations directory. The workflow requires every new table to enable Row Level Security and include explicit policies for SELECT, INSERT, UPDATE, and DELETE operations.

Update TypeScript types after a Supabase schema change by generating updated Supabase types as part of your local migration workflow. This ensures your application remains type-safe and consistent with the latest Postgres schema modifications.

Yes, you need the Supabase CLI to execute local database migrations safely. The workflow relies on CLI commands to apply local-only db:push and db:reset operations, manage timestamp-ordered SQL files, and enforce RLS policies without risking production data loss.

Yes, you can use this local migration workflow to check migration status and view diffs for your local Supabase database. It supports local schema development tasks including adding tables or columns and verifying migration state before any deployment.

Avoiding direct db push commands prevents risky or destructive schema changes to production data. Enforcing a local-only migration workflow ensures all SQL files, RLS policies, and TypeScript type updates are validated locally first, eliminating accidental production impact.