-
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
feat: Rename build_prices
table, make fields non-nullable
#162
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
build_prices
table, make fields non-nullable
/* | ||
Warnings: | ||
|
||
- You are about to drop the `buildprices` table. If the table is not empty, all the data it contains will be lost. |
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.
Should warnings be removed after the query is updated to use RENAME
instead of DROP
?
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.
Good spot thanks - yes! We should keep relevant warnings (very good for PRs) but remove redundant/incorrect ones. I'll fix this shortly 👍
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.
Please see ced8b00
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.
Thanks for tidying!
* feat: Rename `build_prices` table, make not null * fix: Update code now that field in non-nullable * fix: Drop redundant warning
What does this PR do?
buildprices
table