-
Notifications
You must be signed in to change notification settings - Fork 5
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
chore(migrations): squash migrations #176
Conversation
…es and foreign key constraints This commit adds the initial migration file that creates all the necessary tables and foreign key constraints for the database schema. The migration file includes the creation of tables such as "FormType", "Form", "Question", "InputType", "OptionGroup", "OptionChoice", "Response", and many others. It also includes the creation of unique indexes and foreign key constraints between the tables. The purpose of this commit is to set up the initial database schema and structure for the application. This migration file will be used to create the necessary tables and establish the relationships between them.
The migration files have been squashed into one to improve maintainability and reduce clutter in the project. This change helps to keep the project organized and makes it easier to manage the database migrations.
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.
I tested both cases mentioned above and both were fine.
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.
I migrated and seeded the DB, ran all tests - looks good! I have one question about the instructions in the wiki: where do you execute the pg_dump
command? It wasn't recognized when i tried it. Do you have to be on the postgres CL?
Glad that you were able migrate and the DB too. the |
I'm going ahead and merge this branch into |
Description
This PR squashes all previous migrations into one.
Issue link
86b15t5bm
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:
Useful links
squash migrations wiki page
How to squash migrations in prisma
postgres Docs: pgdump