Skip to content

Resolve schema migration plans under the advisory lock - #6

Merged
brianvarskonst merged 3 commits into
mainfrom
fix/findings-20261002
Oct 2, 2026
Merged

brianvarskonst merged 3 commits into
mainfrom
fix/findings-20261002

Conversation

@brianvarskonst

Copy link
Copy Markdown
Member

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.

@brianvarskonst
brianvarskonst merged commit 53a8da3 into main Oct 2, 2026
5 checks passed
@brianvarskonst
brianvarskonst deleted the fix/findings-20261002 branch October 6, 2026 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant