[
https://issues.apache.org/jira/browse/CALCITE-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086276#comment-18086276
]
Sergey Nuyanzin commented on CALCITE-7567:
------------------------------------------
Merged as
[2f626813d5a956e8a51a3ad2be11e05ac7f3f290|https://github.com/apache/calcite/commit/2f626813d5a956e8a51a3ad2be11e05ac7f3f290]
> LeastRestrictiveSqlType 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
> Priority: Major
> Labels: pull-request-available
>
> 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)
