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 08:58:00 UTC

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

Maksim Zhuravkov created IGNITE-18966:
-----------------------------------------

             Summary: Sql. Custom data type. 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
             Fix For: 3.0.0-beta2


1. Calcite uses ANY type for DEFAULT operator and introduction of custom data type caused a regression broke that rule.
  
2. Nullable attribute is not correctly set for custom data type - it creates a custom data type with nullability = true when it should be false.

3. Use commonTypeForBinaryComparison to convert to/from custom data type in binary comparison operators.




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