-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Value conversion to null in the store generates bad queries #26209
Comments
For equal/non-equal we may be able to do something to convert it to |
@dotnet/efteam I wonder if we should warn if you create a value converter like this. Or maybe even pull the feature. Let's discuss in triage tomorrow. |
Backlog for now. See also #26230. |
Seems like a specific case of #10434/#15979. We should also consider what should happen when a join on the converted values is used. Since |
Similar to #26210, but in this case conversion is from null in the database to non-null in code.
Note that this could be another reason not to convert nulls. I don't expect us to do anything about this in 6.0. Maybe ever.
Value converter replaces nulls in the database with non-value in the model:
Query:
Generates SQL:
Which generates no results because nothing is equal to null in SQL.
Full repro:
The text was updated successfully, but these errors were encountered: