fix plan caching for client-specific views#3672
Merged
joshua-spacetime merged 12 commits intomasterfrom Nov 19, 2025
Merged
Conversation
Shubham8287
reviewed
Nov 17, 2025
Shubham8287
approved these changes
Nov 17, 2025
02a4c0c to
0a881d3
Compare
jdetter
approved these changes
Nov 18, 2025
Collaborator
jdetter
left a comment
There was a problem hiding this comment.
Leaving my review as a CLI code owner, Joshua explained the change and it's not API breaking so this seems fine. I did not test this myself.
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.
Description of Changes
Fixes a subscription plan caching bug related to client-specific views.
Before this fix, you could define a client-specific view:
And subscribe to it as follows:
Note this view is implicitly parameterized by
:sender, however when generating a query hash for this subscription, this fact would not be taken into account which would result in this query being cached and reused for all callers.After this fix, a query hash is generated for this subscription as though it were given as:
API and ABI breaking changes
None
Note for CLI code owners:
I had to touch the
subscribecli command file. No updates to the api. It just needed to be updated to look for views in the module def.Expected complexity level and risk
1
Testing