-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
fix(product): when running migrations, prevent exploding on isolated case #5643
Conversation
🦋 Changeset detectedLatest commit: a11fc33 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Ignored Deployments
|
@adrien2p - I'm not sure why this is here, but if its needed, I added a non exploding sql to check if table exists. |
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.
LGTM!
Now that we have the if exists or not exists everywhere, couldn't we remove this totally? |
PS: I love the changeset name "complain" 😂 |
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.
LGTM
what:
When executing the SQL in migrations, its currently throwing an error when products dont exist, but the catch is not stopping the migration from going through the fail route.