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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: sql
• Labels: calcite2-required ignite-3
• Epic Link: SQL. Custom types support 3.0
• Assignee: Maksim Zhuravkov
• Reporter: Maksim Zhuravkov
• Created: 06/Mar/23 08:57
• Updated: 04/Sep/24 16:11
• Resolved: 16/Mar/23 07:35

Description

1. Calcite uses ANY type for the DEFAULT operator and introduction of custom data types 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.

Issue Links

• links to: GitHub Pull Request #1777
• links to: https://github.com/apache/ignite-3/pull/1777