[
https://issues.apache.org/jira/browse/CALCITE-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699285#comment-17699285
]
Sergey Nuyanzin commented on CALCITE-4698:
------------------------------------------
The strange thing I noticed is existence of
{{org.apache.calcite.sql.type.SqlTypeName#MAX_DATETIME_PRECISION}} which is
always 3... Doesn't it make sense to set it to 9 since there are micro and
nanoseconds here?
> Return type of timestampadd(..., ..., timestamp_ltz) should be timestamp_ltz
> instead of timestamp
> -------------------------------------------------------------------------------------------------
>
> Key: CALCITE-4698
> URL: https://issues.apache.org/jira/browse/CALCITE-4698
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Caizhi Weng
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently {{SqlTimestampAddFunction#deduceType}} does not deal with
> timestamp_ltz type correctly. Return type of {{timestampadd(..., ...,
> timestamp_ltz)}} will be timestamp but it should be timestamp_ltz.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
