[
https://issues.apache.org/jira/browse/CALCITE-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18065016#comment-18065016
]
terran2010 commented on CALCITE-7438:
-------------------------------------
[~julianhyde] I execut sql "select NULLIF(1 + 1, 1) from product" ,now calctie
will converted to sql "SELECT CASE WHEN 1 + 1 = 1 THEN NULL ELSE 1 + 1
END\nFROM `foodmart`.`product`", Not converted as expected to 'SELECT CASE WHEN
2=1 THEN NULL ELSE 2 END \ nFROM ` foodmart `. ` product `',I have doubts about
this. Should the conversion of null if be completely prohibited and not
maintained by default
> Do not rewrite NULLIF to a CASE expression
> ------------------------------------------
>
> Key: CALCITE-7438
> URL: https://issues.apache.org/jira/browse/CALCITE-7438
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.41.0
> Reporter: terran2010
> Priority: Major
>
> When execute sql：
> {code:java}
> select NULLIF(count(brand_name),1) from product{code}
> Calcite will make the following optimizations:
> {code:java}
> SELECT CASE WHEN COUNT(brand_name) = 1 THEN NULL ELSE COUNT(brand_name) END
> FROM foodmart.product{code}
> During the actual execution of the above SQL, COUNT (brandname) will be
> executed twice. Can we consider disabling this optimization
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
