[
https://issues.apache.org/jira/browse/IGNITE-24832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-24832:
--------------------------------------
Summary: Sql. Review the behavior and documentation of the
CURRENT_TIME/CURRENT_TIMESTAMP functions (was: Sql. Fix documentation about
CURRENT_TIME/CURRENT_TIMESTAMP)
> Sql. Review the behavior and documentation of the
> CURRENT_TIME/CURRENT_TIMESTAMP functions
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-24832
> URL: https://issues.apache.org/jira/browse/IGNITE-24832
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> From current documentation
> https://ignite.apache.org/docs/ignite3/latest/sql-reference/operators-and-functions#current_time
> {noformat}
> CURRENT_TIME
> Returns the current time in the session time zone, in a value of datatype
> TIMESTAMP WITH TIME ZONE.
> CURRENT_TIMESTAMP
> Returns the current date and time in the session time zone, in a value of
> datatype TIMESTAMP WITH TIME ZONE.
> {noformat}
> # CURRENT_TIME must return {{TIME WITH TIME ZONE}} (not TIMESTAMP)
> # AI3 currently doesn't support TIME WITH TIME ZONE and TIMESTAMP WITH TIME
> ZONE data types
> -We should fix the documentation and note that currently call to
> {{CURRENT_TIME}}, {{CURRENT_TIMESTAMP}} is equivalent to call {{LOCALTIME}},
> {{LOCALTIMESTAMP}} respectively.-
> The only difference between LOCALTIMESTAMP/LOCALTIME and
> CURRENT_TIMESTAMP/CURRENT_TIME is is the return types.
> But currently we return the same types.
> Possible solution:
> # return {{TIMESTAMP WITH LOCAL TIME ZONE}} for {{CURRENT_TIMESTAMP}}
> # remove {{CURRENT_TIME}} as unsupported.
> # fix the documentation accordingly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
