Enable tag fast path on EF Core - #843
Open
waf wants to merge 2 commits into
Open
Conversation
Use IsCommandInfoOptionalForCacheKey in the EFCORE branch of GetCacheKey (the behaviour already exists in EF6). When the option is enabled, the tags become the only information available to build the cache key. Also validate that UseFirstTagAsCacheKey or UseTagsAsCacheKey is enabled.
Member
|
Thank you @waf for the pull request, My developer will look at it. Best Regards, Jon |
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.
EF6 has a "fast path" for
IsCommandInfoOptionalForCacheKey, but as far as I can tell EF Core doesn't use it. This wires up the property for the EF Core path too.