-
Notifications
You must be signed in to change notification settings - Fork 0
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
Schema fixes and backend #71
Conversation
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
This reverts commit 83bb95c.
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
…rchy Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
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.
Do we need the snapshots and migrations?
Also, @adi-lux and @KevinWu098, can you decide on the location for migrations. because it looks like your PRs disagree on that.
Maybe we could just remove the snapshots and migrations for now and readd them before a 1.0 release? I think putting the migrations inside the db folder works, but I'm fine with either |
Yeah that's fine. |
Also, is this ready for review? If so, can you resolve the merge conflicts? |
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Fixed everything, should be good to merge. I think the deploy to staging thing fails because there is no actual database url to migrate to. |
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.
A few more non-blocking comments on one-line fixes
Are you sure? The deployment worked until you merged |
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
…o aa/schema-fixes-and-backend
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Signed-off-by: Adithya Anandsaikrishnan <[email protected]>
Finally fixed it, turns out the problem was in the postinstall script and not the DB url. |
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.
Seems alright
Description
Fixing schema issues as well as problems within the initial drizzle migration.
Issues