Add batch queries support to improve performance and handle row limitations#22
Open
t4nz wants to merge 1 commit into
Open
Add batch queries support to improve performance and handle row limitations#22t4nz wants to merge 1 commit into
t4nz wants to merge 1 commit into
Conversation
…tch processing support
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.
This pull request introduces batch query logic to the WP REST Cache plugin. The goal is to enhance query performance and ensure compatibility with environments that impose per-query row limits (e.g., PlanetScale, which limits rows returned, updated, or deleted to 100k).
Changes included
• Implemented batch queries to split large database operations into smaller chunks.
• Ensures queries respect per-query row limitations imposed by some database environments.
• Improved performance for large datasets by processing queries in batches.
• Added safeguards to maintain data consistency during batched operations.
Benefits
• Prevents query failures in environments with strict row limits.
• Improves stability and compatibility with cloud-hosted databases (e.g., PlanetScale).
• Enhances performance for large-scale cache operations.
Notes
• Backward compatible — existing installations will continue to function without configuration changes.
• Tested with large datasets to validate performance improvements and stability.