Repository navigation
Cache: invalidate core-table facades after native WordPress writes. - #1
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
1 participant
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.
WordPress can update its own tables without going through a BerlinDB Query. A cached
WPCoreTables\Queries\Postsread could therefore return the old title afterwp_update_post(). Listen to WordPress's native mutation hooks and flush the affected facade cache groups, including by-ID rows and secondary lookups. The hook map covers posts, comments, users, terms, term relationships, metadata, options, and links.On object-cache drop-ins without group-flush support, the plugin falls back to a full cache flush for correctness. This is a performance tradeoff for those drop-ins and is documented in the README.
Verified against WordPress 6.7, PHP 8.2, MariaDB 10.2, and core PR #259: 25 tests / 50 assertions, including native post, metadata, user, option, and term-assignment regression tests. PHPStan and Composer validation pass.