[
https://issues.apache.org/jira/browse/IGNITE-23684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901854#comment-17901854
]
Ignite TC Bot commented on IGNITE-23684:
----------------------------------------
{panel:title=Branch: [pull/11674/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11674/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8177346&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Lack of date formatting functions
> -------------------------------------------------
>
> Key: IGNITE-23684
> URL: https://issues.apache.org/jira/browse/IGNITE-23684
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the Calcite SQL engine we don't have any date/time/number formating
> function, and date/time/number parsing functions with custom format.
> H2 engine has TO_DATE, TO_CHAR, TO_NUMBER (Oracle compatible) and own
> FORMATDATETIME, PARSEDATETIME.
> Apache Calcite has TO_DATE and TO_CHAR functions in internal library, but not
> exposed to our SQL engine now. Also it supports CAST(... AS DATE FORMAT ...),
> but we also don't support this syntax.
> Both TO_DATE and CAST-FORMAT are not part of SQL standard, but, perhaps it's
> better to implement TO_DATE (also TO_CHAR, TO_NUMBER) for compatibility with
> H2 engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
