[
https://issues.apache.org/jira/browse/IGNITE-21822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835177#comment-17835177
]
Pavel Pereslegin commented on IGNITE-21822:
-------------------------------------------
Need to ensure that using a public API {{TIMESTAMP WITH LOCAL TIME ZONE}}
literal stores the value, taking into account the client's time zone (such test
already exists - {{ItCommonApiTest#checkTimestampOperations}}, but it must be
executed not in GMT/UTC timezone, it seems that TeamCity runs in GMT).
> Sql. Allow to set time zone on per statement basis
> --------------------------------------------------
>
> Key: IGNITE-21822
> URL: https://issues.apache.org/jira/browse/IGNITE-21822
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> In IGNITE-21551, support for time zone was added to the sql engine. However,
> only Session was updated, while Statement was left intact. Let's eliminate
> such a discrepancy by providing an ability to set time zone on per statement
> basis.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
