-
Notifications
You must be signed in to change notification settings - Fork 453
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
Incorrect SQL generated over 'Contains' in array having null element #3986
Comments
@MaceWindu , this issue is quite serious, is there a way to move it to some service pack of version 4, but not to the version 5.x, which I think is far from the release? |
5.0 release scheduled for tomorrow and I plan to look at this issue later today |
It's a part I'm familiar with. |
Oh wait, it's not a complete fix, it introduces a different bug. :( -> I'm gonna write a comment with what remains to be done in the PR. |
Ok, I thought there was a bug but there is not. |
Describe your issue
Consider the following table
with the following data:
and with the following class generated:
Steps to reproduce
Consider the following test:
The condition over the table 'Issue' should obviously lead to a query that returns no rows. But that's not the case, the record (0, null) is actually returned.
The bug is pretty clear, below is the SQL generated by linq2db and we can see that the necessary brackets are missed there.
Environment details
Linq To DB
version: 4.4.1Database (with version): Postgres 14.1
The text was updated successfully, but these errors were encountered: