You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2026/05/31 17:27:00 UTC

[jira] [Created] (CALCITE-7567) LeastRetrictiveSqlType for TIMESTAMP, TIMESTAMP_LTZ might ignore precision

Sergey Nuyanzin created CALCITE-7567:
----------------------------------------

             Summary: LeastRetrictiveSqlType for TIMESTAMP, TIMESTAMP_LTZ might ignore precision
                 Key: CALCITE-7567
                 URL: https://issues.apache.org/jira/browse/CALCITE-7567
             Project: Calcite
          Issue Type: Bug
          Components: core
            Reporter: Sergey Nuyanzin
            Assignee: Sergey Nuyanzin


The issue is that if there is {{TIMESTAMP}} and {{TIMESTAMP_LTZ}} with different precision 
for instance {{TIMESTAMP(3)}} and {{TIMESTAMP_LTZ(0)}}
{{leastRestrictive}} from TIMESTAMP(3) and TIMESTAMP_LTZ(0)
and {{leastRestrictive}} from TIMESTAMP_LTZ(0) and TIMESTAMP(3)
return different results.
In the latest one there will be leastRestrictive with precision 0



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