data-migration-expert

To validate database migrations, verify ID mappings and check for swapped values or orphaned associations against production reality, ensuring data integrity during schema changes. Explicit SQL queries are required to confirm production data verification.

Rollback safety during a schema change requires a clear rollback plan that reverses data backfills and column renames. Assess migration scripts to verify that a safe rollback procedure is explicitly defined before deployment.

When renaming a database column, check for swapped values, incomplete dual-writes, and orphaned associations. Validate that the mapping to the new column aligns with actual production data rather than just test fixtures.

Yes, explicit SQL queries are required for production data verification. Providing these queries allows the migration analysis to check that ID mappings and data backfills align with actual production reality to prevent data corruption.

The best way to review a database backfill pull request is to validate the script against production data, checking for swapped values and verifying rollback safety. Ensure the plan includes explicit data verification queries and a rollback procedure.

Data migration passes fixtures but corrupts production data when ID mappings are not validated against production reality. Incomplete dual-writes and swapped values often go undetected without explicit SQL production data checks.