You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2023/03/06 10:00:00 UTC

[jira] [Updated] (IGNITE-18969) Sql. Implement of leastRestrictiveType for custom data types within the same type family.

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

Maksim Zhuravkov updated IGNITE-18969:
--------------------------------------
    Summary: Sql. Implement of leastRestrictiveType for custom data types within the same type family.  (was: Sql. Implement of leastRestrictiveType for custom data types.)

> Sql. Implement of leastRestrictiveType for custom data types within the same type family.
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18969
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18969
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Maksim Zhuravkov
>            Priority: Minor
>              Labels: calcite3-required, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> The current implement of IgniteTypeFactory::leastRestrictiveType returns the first custom data type it encounters, which is obviously not correct.
> Add generic rules on how `leastRestrictiveType` should work for some custom data type (e.g. when a type has precision it possible to choose such, when type do not have precision, etc).



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