Fix rolling back columns with indices for SQLite and SQL Server #2128
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
MasterOdin
approved these changes
Nov 30, 2022
MasterOdin
changed the title
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.
Instead of adding a new test for just this one problem, I've updated the existing reversible migrations test (it includes the problematic case of adding a column with an index to an existing table) and made it cross DBMS compatible, to add some more coverage in the process.
AFAICT, previously only MySQL was used except in one test for Postgres. Going forward, adding more cross DBMS coverage probably wouldn't hurt, so that finding DBMS specific issues becomes a bit easier.
refs #2126