-
Notifications
You must be signed in to change notification settings - Fork 934
Proper query plan caching for DML LINQ queries #2299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment has been minimized.
This comment has been minimized.
We would have better to wait for #2300 to be merged, in order to check everything is ok once combined together in master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing my mind, we should merge it first, since merging 5.2.7 to master without this fix would cause a test from 5.2.7 to fail.
Sorry, I have missed cleaning the commit details auto-generated by the squash. |
The resulting commit message details was too misleading (speaking of reverting a thing while no more reverting it: the code was reverted, but no more the feature change). Since the merge was recent and very few people were likely to have already got it, I have disabled the branch protection temporarily and forced pushed a reword. |
This seems to have some side effect - all PRs on master are recently updated |
Properly fixes #2222 by including modified property names in to query key (see #2300 (comment) for details)