Skip to main content
Keep versioned SQL migrations in the application’s configured directory, with filenames YYYYMMDDHHMMSS_name.sql. Check the current init output for the exact required naming and capability contract. Prefer additive changes: introduce a nullable column, deploy compatible code, backfill existing rows, then review removal or stronger constraints separately. Test against existing records before promotion. Never replace production data with a Dev dump to synchronize schemas. Promotion plans show the verified artifact and migration effects. After applying them, check both the new behavior and preservation of existing records. Shared data means the same physical database serves Dev and Prod. Database Skill · Environments · SQL exports