-
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
Refactor database #295
Refactor database #295
Conversation
…ss table, added isArchived to users and specialNote to rides.
…ID in Ride table for a more normalized design.
Hey @Atticusth7 , I have a few inputs:
The only PostgreSQL feature we are using is enums. So, I think we can easily move to SQLite and make our database deployment much easier. We won't have enums available to us in SQLite however, they can be substituted with just strings. We will need to careful to use the right strings in the APIs. Please look at these links to figure out how to migrate: https://www.robinwieruch.de/next-prisma-sqlite/ and https://www.prisma.io/docs/orm/overview/databases/sqlite If y'all have any questions please let me know. |
Hey @TusharW4ni, I belive that we are not using the endTime and @Atticusth7 will be removing it from the database. Thank you! |
Alright, a few more things:
Since I opened this PR, I don't think GitHub will let me merge it in. So, I've added you as a reviewer on the PR. After making these changes, see if you are able to hit the |
…eeded the db, formatted schema
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed changes and approved review.
No description provided.