#1152 - fire the operation events before after retrieving a query result even if it is cached #1153
Conversation
This file contains 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
…ng a query result even if it is cached
|
It'd be useful if we could distinguish in the event between a cached execution and an uncached execution. Either that or to have separate events for the two. This is especially useful if you want to do performance measurements since a cached query will behave differently from an uncached query. |
Kingdutch
approved these changes
Mar 26, 2021
|
This completely fixes my language negotiation problems as well. The approach seems to be valid. +1 for merging this! |
|
@hchonov and @Kingdutch It would be very nice if we could get this in the next release! |
|
@dbosen I think that we could go with the current solution and add a |
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.
Closes #1152