Fixed migration causing issues with mariadb #16028
Merged
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.
This PR amends a migration that was included in #15714 that does not work on older versions of mariadb (v10 and below I believe).
That PR introduced a
json
column and mariadb (<v11) doesn't like that so this PR changes it to a text type like we have elsewhere in the application.Some people may have already successfully run the migration and so another migration was created to "change" the column to
text
. To the best of my knowledge and from testing, if the column is alreadytext
then the operation is essentially a no-op so it shouldn't cause any issues "changing" the column from "text" to "text".Fixes #16015