[
https://issues.apache.org/jira/browse/CALCITE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316761#comment-15316761
]
Jacques Nadeau commented on CALCITE-1268:
-----------------------------------------
In response to Julian's questions: yes, I think it should be the complete
coercion. That includes type and nullability, precision and length. The union
operation should get two identical schema inputs (ignoring field names).
> Union should apply explicit Project over its children if they have different
> but coercible types
> ------------------------------------------------------------------------------------------------
>
> Key: CALCITE-1268
> URL: https://issues.apache.org/jira/browse/CALCITE-1268
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.7.0
> Reporter: Maryann Xue
> Assignee: Maryann Xue
>
> Test case in SqlToRelConverterTest:
> {code}
> @Test public void testUnionExprTypes() {
> check(
> "select empno, sal from emp "
> + "union all "
> + "select deptno, deptno from dept",
> "${plan}");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
