[release/8.0] Stop using case-insensitive comparisons for indexed properties (#32899) #32919
Conversation
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
Fixes #32898 Note that we didn't change what we do in the update pipeline, which appears to already be using provider values.
ajcvickers
changed the title
|
Note that the branch is currently closed |
maumar
approved these changes
Feb 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Port of #32899
Fixes #32898
Description
EF8 contained a small enhancement to match SQL Server defaults and do case-insensitive comparisons by default. This change also included properties with indexes, which was a mistake.
Customer impact
Customers get incorrect change detection, resulting in possible corrupted data, on index properties.
How found
Customer reported on 8.
Regression
Yes, from 7.
Testing
Tests added.
Risk
Low. Quirked.