[
https://issues.apache.org/jira/browse/CALCITE-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816959#comment-16816959
]
Stamatis Zampetakis commented on CALCITE-2994:
----------------------------------------------
It is exactly as [~Chunwei Lei] said. I have already the fix for it but I
cannot push it before Monday (family restrictions :)). How about doing the
review on it? Otherwise, you can push the fix and I will do the review on
Monday. As you want ;)
> Least restrictive type among structs does not consider nullability
> -------------------------------------------------------------------
>
> Key: CALCITE-2994
> URL: https://issues.apache.org/jira/browse/CALCITE-2994
> Project: Calcite
> Issue Type: Bug
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Fix For: 1.20.0
>
>
> Consider the following high-level example:
> {code:sql}
> CREATE TYPE Coordinates AS (
> x INT,
> y INT);
> CREATE TABLE Address (
> loc1 Coordinates NOT NULL,
> loc2 Coordinates)
> {code}
> The least restrictive type between loc1 and loc2 is the type of loc2 (i.e., a
> nullable Coordinates type).
> The existing code (i.e., RelDataTypeFactory#leastRestrictive) does take into
> account nullability when the type is structured type (or row type).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
