[Adjustment] Update new migrations not to execute if the changes already exist in db #12364
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GSadee
added
DX
lchrusciel
approved these changes
Feb 17, 2021
|
I'm only wondering if we should cover the same case for |
|
Thanks, Grzegorz! 🎉 |
GSadee
added a commit
that referenced
this pull request
Feb 17, 2021
…o execute if the changes already exist in db (GSadee) This PR was merged into the 1.9 branch. Discussion ---------- | Q | A | --------------- | ----- | Branch? | 1.9 | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Related tickets | fixes #12364 (comment) | License | MIT Commits ------- 41fe59e [Adjustment] Update down methods of new migrations not to execute if the changes already exist in db
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm adding these
ifstatements not to execute migrations if the changes already exist in the database. It could resolve potential problems for upgrading Sylius from 1.8 to 1.9 with installed the newest RefundPlugin.