Skip to content

[TINY] Fix to #23121 - Query: improve optimization of "false==(expr)" #23239

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Nov 12, 2020

Conversation

maumar
Copy link
Contributor

@maumar maumar commented Nov 9, 2020

When optimizing false == x -> !x we were not running optimization for the Not that we just created, like we do for x == false

Fixes #23121

@maumar maumar changed the title Fix to #23121 - Query: improve optimization of "false==(expr)" [TINY] Fix to #23121 - Query: improve optimization of "false==(expr)" Nov 9, 2020
@maumar maumar requested a review from smitpatel November 9, 2020 07:28
@dmitry-lipetsk
Copy link
Contributor

Works fine :)

Thanks!

When optimizing false == x -> !x we were not running optimization for the Not that we just created, like we do for x == false

Fixes #23121
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Query: improve optimization of "false==(expr)"
3 participants