[
https://issues.apache.org/jira/browse/CALCITE-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-5478.
----------------------------------
Fix Version/s: 1.34.0
Resolution: Fixed
Fixed in
[29fcbf14|https://github.com/apache/calcite/commit/29fcbf14f1c8f83ca27d307d4b458efa0d4ece5f].
> Use highest input precision for datetimes in
> SqlTypeFactoryImpl.leastRestrictive
> --------------------------------------------------------------------------------
>
> Key: CALCITE-5478
> URL: https://issues.apache.org/jira/browse/CALCITE-5478
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Gian Merlino
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.34.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> For example: {{leastRestrictive(TIMESTAMP(3), TIMESTAMP(0))}} would be
> {{TIMESTAMP(3)}}, not {{TIMESTAMP(0)}}.
> Some code exists to do this for other types, but not datetimes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
