Skip to content
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

Fix precedence issue when it comes to expressions like boolParam = nullableBoolColumn IS NOT NULL #1311

Merged
merged 2 commits into from
Jan 26, 2021

Conversation

lauxjpn
Copy link
Collaborator

@lauxjpn lauxjpn commented Jan 26, 2021

Fixes #1309

@lauxjpn lauxjpn added this to the 5.0.0-alpha.3 milestone Jan 26, 2021
@lauxjpn lauxjpn self-assigned this Jan 26, 2021
@lauxjpn lauxjpn merged commit e2cd0e9 into PomeloFoundation:master Jan 26, 2021
@lauxjpn lauxjpn deleted the fix/issue1309 branch January 26, 2021 17:36
lauxjpn added a commit to lauxjpn/Pomelo.EntityFrameworkCore.MySql that referenced this pull request Jan 26, 2021
lauxjpn added a commit that referenced this pull request Jan 26, 2021
…lParam = nullableBoolColumn IS NOT NULL` (#1312)

* Backport: Fix precedence issue when it comes to expressions like `boolParam = nullableBoolColumn IS NOT NULL` (#1311)

* Implement changes for EF Core 3.1 and fix tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nullable boolean in MySQL condition always yielding false/true
1 participant