[jira] [Updated] (IGNITE-18966) Sql. Custom data types. Fix least restrictive type and nullability.

["Maksim Zhuravkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Zhuravkov updated IGNITE-18966:
--------------------------------------
    Summary: Sql. Custom data types. Fix least restrictive type and nullability.  (was: Sql. Custom data type. Fix least restrictive type and nullability.)

> Sql. Custom data types. Fix least restrictive type and nullability.
> -------------------------------------------------------------------
>
>                 Key: IGNITE-18966
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18966
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Maksim Zhuravkov
>            Priority: Minor
>              Labels: calcite2-required, calcite3-required, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> 1. Calcite uses ANY type for DEFAULT operator and introduction of custom datas type caused a regression that broke that rule.
>   
> 2. Nullable attribute is not correctly set for custom data types - it creates a custom data type with nullability = true when it should be false.
> 3. Update commonTypeForBinaryComparison to convert to/from custom data type in binary comparison operators.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)