[
https://issues.apache.org/jira/browse/IGNITE-25190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Dmitrienko updated IGNITE-25190:
-----------------------------------------
Summary: Current timestamp / date adjusted to user time zone when cast to
varchar (was: CURRENT_TIMESTAMP adjusted to user time zone when cast to
VARCHAR)
> Current timestamp / date adjusted to user time zone when cast to varchar
> ------------------------------------------------------------------------
>
> Key: IGNITE-25190
> URL: https://issues.apache.org/jira/browse/IGNITE-25190
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Vladimir Dmitrienko
> Priority: Major
>
> The query {{SELECT CURRENT_TIMESTAMP;}} returns the current timestamp in the
> UTC+0 time zone, as expected. However, when the timestamp is cast to
> {{{}VARCHAR{}}}, it is automatically adjusted to the user's local time zone,
> which leads to inconsistent behavior.
> Example:
> {code:java}
> SELECT CURRENT_TIMESTAMP;
> // 2025-04-18T10:19:12.719Z
> SELECT CURRENT_TIMESTAMP::VARCHAR;
> // 2025-04-18 12:19:17.68 Europe/Warsaw{code}
> {*}Note{*}: the {{CURRENT_DATE}} is affected in the same manner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
