[
https://issues.apache.org/jira/browse/IGNITE-24832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-24832:
--------------------------------------
Fix Version/s: 3.1
> 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
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
> 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 (we don't support "TIME WITH..."
> now IGNITE-21555).
> # fix the documentation accordingly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
