Repository navigation
Resolve schema migration plans under the advisory lock - #6
Merged
Merged
Conversation
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
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.
SQL for a deferred schema migration is now resolved after acquiring the database advisory lock. The live database schema is read under the same lock before destructive-change checks, transaction classification and execution. Locks are released when resolution fails. Existing SQL executors retain their interface through an additive deferred-operation contract.
Validation: coding standards, PHPStan and PHPUnit (65 tests / 444 assertions); isolated real MariaDB migration tests (6 tests / 77 assertions); independent review. The new API supports the ORM schema-diff fix and is prepared for v1.0.4.