[
https://issues.apache.org/jira/browse/CALCITE-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149716#comment-17149716
]
Julian Hyde edited comment on CALCITE-4099 at 7/1/20, 10:11 PM:
----------------------------------------------------------------
NullPolicy and Strong represent arrows in different directions - null policy
says whether an expression is null *if* its input is null, and strong says
whether the expression is null *only if* its input is null.
So, unifying them might not be trivial. The unified enum would certainly have
more cases than either of the original 2 enums.
But yes, unifying them would be great, if you can do it without making things
more complicated.
was (Author: julianhyde):
NullPolicy and Strong represent arrows in different directions - null policy
says whether an expression is null *if* its input is null, and strong says
whether the expression is null *only if* its input is null.
So, unifying them might not be trivial. The unified enum would certainly have
more cases than either of the original 2 enums.
> Unify Strong.Policy and NullPolicy
> ----------------------------------
>
> Key: CALCITE-4099
> URL: https://issues.apache.org/jira/browse/CALCITE-4099
> Project: Calcite
> Issue Type: Task
> Components: core
> Reporter: Ruben Q L
> Priority: Minor
>
> (discussion about this ticket started in CALCITE-4094)
> {{Strong.Policy}} and {{NullPolicy}} are two different enum that represent
> grosso-modo the same thing. The former is mostly used on the simplifier, and
> the latter on the code generation.
> To be studied if we could unify both entities and make it available through
> the SqlOperator.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
