Skip migrate-to-gutentag migration for fresh installs #1381
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
|
Build will be fixed by #1383 |
On fresh installs the alchemy installer installs all engines migrations, including the Gutentag tables. We then already have all the tables and indexes we need, so we can skip the migration that is meant for existing Alchemy installations.
tvdeyen
force-pushed
the
skip-gutentag-migration
branch
from
251bf58
to
54a42fd
Compare
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.
On fresh installs the alchemy installer installs all engines migrations, including the Gutentag tables. We then already have all the tables and indexes we need, so we can skip the migration that is meant for existing Alchemy installations.
Fixes #1379