[
https://issues.apache.org/jira/browse/IGNITE-25319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-25319:
--------------------------------------
Description:
Supported fields (SQL 2023):
{noformat}
<datetime template year> ::= YYYY | YYY | YY | Y
<datetime template rounded year> ::= RRRR | RR
<datetime template month> ::= MM
<datetime template day of month> ::= DD
<datetime template day of year> ::= DDD
{noformat}
But calcite's SimpleDateFormat based parser accepts almost everything. MMM,
DDDD, etc.
was:
Supported fields (SQL 2023):
{noformat}
<datetime template year> ::= YYYY | YYY | YY | Y
<datetime template rounded year> ::= RRRR | RR
<datetime template month> ::= MM
<datetime template day of month> ::= DD
<datetime template day of year> ::= DDD
{noformat}
But calcite's SimpleDateFormat based parser accepts almost everything. MMM,
DDDD, etc.
> Sql. Cast FORMAT. Date, Timestamp, Timestamp LTZ. Parse accepts invalid year,
> month, day values
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-25319
> URL: https://issues.apache.org/jira/browse/IGNITE-25319
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
>
> Supported fields (SQL 2023):
> {noformat}
> <datetime template year> ::= YYYY | YYY | YY | Y
> <datetime template rounded year> ::= RRRR | RR
> <datetime template month> ::= MM
> <datetime template day of month> ::= DD
> <datetime template day of year> ::= DDD
> {noformat}
> But calcite's SimpleDateFormat based parser accepts almost everything. MMM,
> DDDD, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
