fix(mock-vc-issuer): use db push instead of migrate deploy #296
+15
−1
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
- Change entrypoint to use `prisma db push --accept-data-loss` for schema sync - Update package-lock.json with peer dependency markers Using db push is simpler for development/demo environments where migration history tracking is not required. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Contributor
JorisHeadease
left a comment
JorisHeadease
left a comment
There was a problem hiding this comment.
Quite a scary change, but as long as it's strictly for mock implementations and we don't care about migrations and data loss..
What is the actual issue with using prisma migrations? If you're certain it's not worth the time to fix, and there's no real risk of losing important data, feel free to merge it in.
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.
Summary
prisma migrate deploytoprisma db pushfor database schema synchronizationChanges
db push --accept-data-lossinstead ofmigrate deployWhy
db pushis simpler for development/demo environments where migration history tracking is not required. It directly syncs the schema to the database without requiring migration files.