seed-safety

To prevent duplicate database seeding, you need an idempotent execution protocol that checks known identifiers like slugs or SKUs against existing records before running. This ensures scripts only add the expected data delta without creating overlapping entries.

Idempotent database seeding is a safe execution method that captures a baseline row count, runs the seed script exactly once, and verifies the post-run count matches the expected delta. This prevents accidental data loss or duplicate insertions during repeated migrations.

Safe Prisma migration execution requires validating your working directory, capturing a pre-flight row count, running the command once, and immediately verifying the post-run count. If counts mismatch, block re-runs and investigate anomalies before proceeding.

When database seed verification fails and row counts mismatch, block any re-runs immediately. Investigate for duplicate records or data anomalies, and wait for explicit user direction before attempting any cleanup or rollback procedures.

To check for data overlap before a migration, perform a pre-flight baseline check using known identifiers like slugs, names, or SKUs. This detects existing entries in the target table to prevent duplicate seeding and ensure safe execution.

Running database seeds multiple times requires idempotent execution with pre-flight baseline checks and post-run verification to ensure data integrity. If a failure occurs with ambiguous results, block any re-run to prevent corruption until the issue is resolved.