-
Notifications
You must be signed in to change notification settings - Fork 214
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
Jsonb column property null check result in wrong SQL condition #1674
Comments
@VendelCzinder thanks, found the issue and submitted a fix for 5.0.3. The issue is perfect, contains all the info :) |
Note, this is very similar to #1683, but that one is for arrays whereas this one is for JSON. |
roji
added a commit
to roji/efcore.pg
that referenced
this issue
May 16, 2021
roji
added a commit
that referenced
this issue
May 16, 2021
roji
added a commit
that referenced
this issue
May 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have a problem where newer versions of Npgsql for EF creates wrong SQL query conditions. See the example below.
Minimal working example:
.NET:
SQL:
Resulting SQL query using Npgsql.EntityFrameworkCore.PostgreSQL version 3.1.11:
Resulting SQL query using Npgsql.EntityFrameworkCore.PostgreSQL version 5.0.X:
Please note the "WHERE FALSE" condition, that results in an empty result set regardless of the real table data.
PostgreSQL version: 10.15
.NET version: 5.0
Any thoughts?
Best Regards,
Vendel
(this is my first ticket, please tell if there is a problem with it)
The text was updated successfully, but these errors were encountered: