Ensure the order of database updates shown is consistent with how it would actually run - #6376
Open
codebymikey wants to merge 3 commits into
Open
Ensure the order of database updates shown is consistent with how it would actually run#6376codebymikey wants to merge 3 commits into
codebymikey wants to merge 3 commits into
Conversation
Member
|
I notice that this is in Draft. Please remove draft whenever this is ready for review. No rush. Thanks. |
codebymikey
force-pushed
the
consistent-db-update-order
branch
from
October 10, 2025 13:58
a0454e8 to
1a52962
Compare
codebymikey
marked this pull request as ready for review
October 10, 2025 17:01
codebymikey
requested review from
greg-1-anderson,
pfrenssen and
weitzman
as code owners
October 10, 2025 17:01
Contributor
Author
|
Added the tests, current upstream failures are related to the https://www.drupal.org/project/drupal/issues/3447617 issue. |
Member
|
This looks like an excellent improvement Thanks for the tests. Alas, this PR has to go into 14.x as well and there have been a few changes there (symfony console related). Whats easiest? Want me to merge this and would you be available to make a 14.x PR? |
codebymikey
force-pushed
the
consistent-db-update-order
branch
from
February 20, 2026 18:06
c6eff6d to
0a7cdc2
Compare
Contributor
Author
|
Yeah, that's fine. I've updated the PR, and created a sibling PR targetting 14.x. |
codebymikey
force-pushed
the
consistent-db-update-order
branch
from
April 21, 2026 10:06
73edcf3 to
c91bed4
Compare
Contributor
Author
|
Can this PR please be reviewed? Just so it doesn't get out of sync with the main branch |
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.
Currently the database update is listed in alphabetical order, rather than the actual order it would run.
This is especially the case when the
hook_update_dependencieshook is incorporated.Still need tests and some minor coding standards fixes, but pushing this up just so I don't lose/forget it.