Repository navigation
chore: force wipe database before seeding - #19
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR makes the Prisma seed script strictly idempotent by forcefully wiping all existing data from the database using Prisma 8's raw execution lane (
db.runtime().execute) before inserting the mock data.This means
pnpm run seedcan now be run repeatedly to completely reset the local database without hitting unique constraint errors.Changes
src/prisma/seed.ts: Replaced simple.create()flow with explicit rawDELETE FROMstatements..env.example: Updated the default connection string fromlocalhostto127.0.0.1to prevent IPv6/IPv4 binding issues (EPERM) on macOS when using the pure-JSpgdriver.