fix: re-seeding should not append the data in master table #460
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.
What
Why
How
To address this issue, follow these steps:
Identify the master record for which re-seeding is being performed. This is typically a record that serves as a primary reference point in the database.
Before re-seeding, implement a check to verify if the data already exists for the identified master record. This can be done by querying the database using Prisma to check for existing data associated with the master record.
Modify the re-seeding process to conditionally insert data only if it does not already exist. This can be achieved by using Prisma's findUnique or findFirst functions to check for the presence of the master record before attempting to insert new data.