You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2023/06/16 16:59:00 UTC
[jira] [Resolved] (CALCITE-5761) DATE_TRUNC compile-time evaluation produces wrong results
[ https://issues.apache.org/jira/browse/CALCITE-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde resolved CALCITE-5761.
----------------------------------
Fix Version/s: 1.35.0
Resolution: Fixed
Fixed in [4b37ed37|https://github.com/apache/calcite/commit/4b37ed377a08953822ccff105c8ba53cd57b94fe]; thanks for the PR, [~mbudiu]!
> DATE_TRUNC compile-time evaluation produces wrong results
> ---------------------------------------------------------
>
> Key: CALCITE-5761
> URL: https://issues.apache.org/jira/browse/CALCITE-5761
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.34.0
> Reporter: Mihai Budiu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.35.0
>
>
> Adding the following 3 tests to SqlOperatorTest.testDateTrunc produces assertion failures.
> f.checkScalar("date_trunc(date '2015-02-19', decade)",
> "2010-01-01", "DATE NOT NULL");
> f.checkScalar("date_trunc(date '2015-02-19', century)",
> "2001-01-01", "DATE NOT NULL");
> f.checkScalar("date_trunc(date '2015-02-19', millennium)",
> "1001-01-01", "DATE NOT NULL");
> Results produced:
> Query: values (date_trunc(date '2015-02-19', decade))
> Expected: is "2010-01-01"
> but: was "2015-01-05"
> Query: values (date_trunc(date '2015-02-19', century))
> Expected: is "2001-01-01"
> but: was "2012-09-17"
> Query: values (date_trunc(date '2015-02-19', millennium))
> Expected: is "1001-01-01"
> but: was "2002-11-09"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)