-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kazala Prisma -> Drizzle migration #130
Open
jasonappah
wants to merge
26
commits into
dev
Choose a base branch
from
oluwapelps/asu-17-migrate-prisma-to-drizzle
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
Collaborator
jasonappah
commented
Aug 28, 2024
- Initial drizzle setup
- Migrate homepage and event details page endpoint
- Change default import on adapter
- Add drizzle to user ticket endpoint
- Increase drizzle coverage
- Increase drizzle coverage
- More drizzle migrations
- Fix super admin procedure
- Fix lock file
- chore: switch to drizzle postgres adapter
- chore: nextauth adapter + drizzle kit conf -> postgres
- chore: remove pscale dep
- chore: replace mysql imports with pg
- chore: drizzle schema fixes
- chore: generate migrations to sub dir
- fix: map fee holder field to correct col name
- chore: move introspect command to pg
- chore: fix data types + field names
- chore: use callback based pg client connection
- chore: use new drizzle-kit version
- chore: delete drizzle migrations
- chore: match prisma types, fks, indexes in drizzle
- feat(fam): remove leaderboard page
- feat(web): fix event sorting
- feat(web): restore regular theme colors
- fix(family): use correct filename for route handler
as long as both prisma and drizzle are in use side by side, we need to ensure the schemas remain in sync and prisma should be used to create/run migrations until all functionality works in drizzle
# Conflicts: # apps/website/package.json # pnpm-lock.yaml # turbo.json
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.