[
https://issues.apache.org/jira/browse/IGNITE-22032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-22032:
--------------------------------------
Description:
Most databases (see calcite issue) return a json that contains a date string,
but calcite returns its internal representation of date values (number of days
as int)
{code}
SELECT JSON_OBJECT('a': CAST('2010-01-01' AS DATE)) as c1
{"a":14610}
{code}
Expected behaviour:
{code}
SELECT JSON_OBJECT('a': CAST('2010-01-01' AS DATE)) as c1
{"a":"2010-01-01"}
{code}
was:
Most databases (see calcite issue) return a json that contains a date string,
but calcite returns its internal representation of date values (number of days
as int)
{code}
SELECT JSON_OBJECT('a': CAST('2010-01-01' AS DATE)) as c1
{"a":14610}
{code}
> Sql. JSON_OBJECT. Internal representation DATE values leaks into resulting
> JSON object
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-22032
> URL: https://issues.apache.org/jira/browse/IGNITE-22032
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Maksim Zhuravkov
> Priority: Minor
> Labels: ignite-3
>
> Most databases (see calcite issue) return a json that contains a date string,
> but calcite returns its internal representation of date values (number of
> days as int)
> {code}
> SELECT JSON_OBJECT('a': CAST('2010-01-01' AS DATE)) as c1
> {"a":14610}
> {code}
> Expected behaviour:
> {code}
> SELECT JSON_OBJECT('a': CAST('2010-01-01' AS DATE)) as c1
> {"a":"2010-01-01"}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
