Handle multiline statements in migrations#18478
Merged
AndyButland merged 7 commits intov13/devfrom Mar 4, 2025
Merged
Conversation
https://github.com/umbraco/Umbraco-CMS into v13/bugfix/handle-multi-line-statements-in-migrations
Migaroez
reviewed
Mar 4, 2025
src/Umbraco.Infrastructure/Migrations/MigrationExpressionBase.cs
Outdated
Show resolved
Hide resolved
Migaroez
approved these changes
Mar 4, 2025
AndyButland
deleted the
v13/bugfix/handle-multi-line-statements-in-migrations
branch
This was referenced Sep 30, 2025
This was referenced Dec 9, 2025
This was referenced Sep 30, 2025
This was referenced Dec 9, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Prerequisites
Fixes #18477
Description
This fixes the links issue about not supporting multi-line SQL statements in the migrations. The reporter has done all the work here - I've just applied the fix they have already found and verified it.
See the linked issue for a sample you can use to test. When working in source code I just added it to the most recent migration and then used the following SQL to set the state back one step, and then started Umbraco.