Merged
Conversation
Member
|
This should also need to be added in the upgrading under Config section telling people to add the new property. |
Member
Author
|
Updated. |
datamweb
approved these changes
Aug 4, 2025
paulbalandan
reviewed
Aug 5, 2025
5 tasks
michalsn
force-pushed
the
feat/migration-lock
branch
from
6d5e47a to
e562dd3
Compare
Member
|
Thank you, @michalsn |
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
3 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.
Description
This PR introduces a database-agnostic locking system for migrations. It guarantees consistent behavior across all supported databases. Lock cleanup is safe and automatically handled through
finallyblocks, and there are no modifications to the public API, ensuring full compatibility with existing workflows.Closes #9646
Checklist: