You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2025/06/12 11:04:00 UTC

[jira] [Resolved] (IGNITE-25010) Add stricter date patterns validation for CAST FORMAT

     [ https://issues.apache.org/jira/browse/IGNITE-25010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Zhuravkov resolved IGNITE-25010.
---------------------------------------
    Resolution: Fixed

Fixed in https://issues.apache.org/jira/browse/IGNITE-25317

> Add stricter date patterns validation for CAST FORMAT
> -----------------------------------------------------
>
>                 Key: IGNITE-25010
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25010
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> This is clone of https://issues.apache.org/jira/browse/CALCITE-6922 issue
> Currently, when using CAST with FORMAT we can specify strange date/time/timestamp patterns that (I believe) are not SQL standard compliant and which produce confusing results.
> {code:java}
> sql("SELECT CAST('9999999-9999999-9999999' AS DATE FORMAT 'y-MM-dd')");              // -898510-03-05
> sql("SELECT CAST('9999999-9999999-9999999' AS DATE FORMAT 'y-MM-dd')::VARCHAR");     // +0'-0(-.
> {code}



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