LINQ: Fixes NullReferenceException when attempting to generate SQL for a LINQ expression which performs static field or property access #3190
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
… LINQ expression which performs static field or property access (fixes Azure#3188)
notheotherben
requested review from
khdang,
sboshra,
neildsh,
kirankumarkolli,
j82w,
ealsur,
FabianMeiswinkel and
kirillg
as code owners
j82w
approved these changes
May 12, 2022
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
j82w
changed the title
ealsur
approved these changes
May 12, 2022
khdang
approved these changes
May 12, 2022
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.
Description
This PR should fix the issue raised in #3188 in which attempts to access a static field or property (such as
DateTime.UtcNow) within a LINQ-to-SQL expression will result in aNullReferenceException. It does so by correctly handling the presence of anullmember expression when evaluating field and property access.Type of change
Please delete options that are not relevant.
Closing issues
To automatically close an issue: closes #3188