You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Jiatao Tao (Jira)" <ji...@apache.org> on 2021/01/10 10:17:00 UTC
[jira] [Updated] (CALCITE-4458) The "rowTypeCoercion" for "SET"
operations should be "or" relationship
[ https://issues.apache.org/jira/browse/CALCITE-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiatao Tao updated CALCITE-4458:
--------------------------------
Summary: The "rowTypeCoercion" for "SET" operations should be "or" relationship (was: "rowTypeCoercion" for "SET" operations should be or relationship)
> The "rowTypeCoercion" for "SET" operations should be "or" relationship
> ----------------------------------------------------------------------
>
> Key: CALCITE-4458
> URL: https://issues.apache.org/jira/browse/CALCITE-4458
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Jiatao Tao
> Assignee: Jiatao Tao
> Priority: Critical
>
> In org.apache.calcite.sql.validate.implicit.TypeCoercionImpl#rowTypeCoercion#124:
> {code:java}
> case UNION:
> case INTERSECT:
> case EXCEPT:
> // Set operations are binary for now.
> final SqlCall operand0 = ((SqlCall) query).operand(0);
> final SqlCall operand1 = ((SqlCall) query).operand(1);
> final boolean coerced = rowTypeCoercion(scope, operand0, columnIndex, targetType)
> && rowTypeCoercion(scope, operand1, columnIndex, targetType);
> {code}
> Seems the coerced should
--
This message was sent by Atlassian Jira
(v8.3.4#803005)