Fixes and improvements to StartsWith/EndsWith/Contains #31482
Merged
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.
x LIKE y
returns true iff x and y are non-null and there's a match; otherwise false (Null semantics compensation missing for LIKE negation #26735).x.EndsWith(y)
now returns true iff x and y are non-null and there's a match; otherwise false. This fixes negation issues such as "Where" clause with "!string.Contains" produces incorrect SQL #30493.@maumar you'll probably want to take a look at this when you're back.
Closes #30493
Closes #11881
Closes #26735
Does part of #26634 (for Like)