[jira] [Updated] (IGNITE-25154) Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
[
https://issues.apache.org/jira/browse/IGNITE-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-25154:
--
Fix Version/s: 3.1
> Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
> ---
>
> Key: IGNITE-25154
> URL: https://issues.apache.org/jira/browse/IGNITE-25154
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following test must result in out of range exception.
> {code:sql}
> SELECT CURRENT_TIME + INTERVAL 292 DAYS
> {code}
> and (with literal)
> {code:sql}
> SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL
> 292 DAYS
> {code}
> Actual result
> {noformat}
> +10018-09-08T21:00:00Z
> {noformat}
> This does not reproduce with TIMESTAMP (WITHOUT TIME ZONE).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-25154) Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
[
https://issues.apache.org/jira/browse/IGNITE-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-25154:
--
Description:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
p.s. the same is applicable for the following:
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS
{code}
was:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS)
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
p.s. the same is applicable for the following:
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS
{code}
> Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
> ---
>
> Key: IGNITE-25154
> URL: https://issues.apache.org/jira/browse/IGNITE-25154
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> The following test must result in out of range exception.
> {code:sql}
> SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL
> 292 DAYS
> {code}
> Actual result
> {noformat}
> +10018-09-08T21:00:00Z
> {noformat}
> This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
> ZONE).
> p.s. the same is applicable for the following:
> {code:sql}
> SELECT CURRENT_TIME + INTERVAL 292 DAYS
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-25154) Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
[
https://issues.apache.org/jira/browse/IGNITE-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-25154:
--
Description:
The following test must result in out of range exception.
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS
{code}
and (with literal)
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with TIMESTAMP (WITHOUT TIME ZONE).
was:
The following test must result in out of range exception.
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS
{code}
and
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
> Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
> ---
>
> Key: IGNITE-25154
> URL: https://issues.apache.org/jira/browse/IGNITE-25154
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> The following test must result in out of range exception.
> {code:sql}
> SELECT CURRENT_TIME + INTERVAL 292 DAYS
> {code}
> and (with literal)
> {code:sql}
> SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL
> 292 DAYS
> {code}
> Actual result
> {noformat}
> +10018-09-08T21:00:00Z
> {noformat}
> This does not reproduce with TIMESTAMP (WITHOUT TIME ZONE).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-25154) Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
[
https://issues.apache.org/jira/browse/IGNITE-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-25154:
--
Description:
The following test must result in out of range exception.
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS
{code}
and
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
was:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
p.s. the same is applicable for the following:
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS
{code}
> Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
> ---
>
> Key: IGNITE-25154
> URL: https://issues.apache.org/jira/browse/IGNITE-25154
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> The following test must result in out of range exception.
> {code:sql}
> SELECT CURRENT_TIME + INTERVAL 292 DAYS
> {code}
> and
> {code:sql}
> SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL
> 292 DAYS
> {code}
> Actual result
> {noformat}
> +10018-09-08T21:00:00Z
> {noformat}
> This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
> ZONE).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-25154) Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
[
https://issues.apache.org/jira/browse/IGNITE-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-25154:
--
Description:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS)
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
p.s. the same is applicable for the following:
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS
{code}
was:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS)
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
p.s. the same is applicable for the following:
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS)
{code}
> Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
> ---
>
> Key: IGNITE-25154
> URL: https://issues.apache.org/jira/browse/IGNITE-25154
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> The following test must result in out of range exception.
> {code:sql}
> SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL
> 292 DAYS)
> {code}
> Actual result
> {noformat}
> +10018-09-08T21:00:00Z
> {noformat}
> This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
> ZONE).
> p.s. the same is applicable for the following:
> {code:sql}
> SELECT CURRENT_TIME + INTERVAL 292 DAYS
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-25154) Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
[
https://issues.apache.org/jira/browse/IGNITE-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-25154:
--
Description:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS)
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
p.s. the same is applicable for the following:
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS)
{code}
was:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS)
{code}
or
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS)
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
> Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
> ---
>
> Key: IGNITE-25154
> URL: https://issues.apache.org/jira/browse/IGNITE-25154
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> The following test must result in out of range exception.
> {code:sql}
> SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL
> 292 DAYS)
> {code}
> Actual result
> {noformat}
> +10018-09-08T21:00:00Z
> {noformat}
> This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
> ZONE).
> p.s. the same is applicable for the following:
> {code:sql}
> SELECT CURRENT_TIME + INTERVAL 292 DAYS)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-25154) Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
[
https://issues.apache.org/jira/browse/IGNITE-25154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-25154:
--
Description:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS)
{code}
or
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS)
{code}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
was:
The following test must result in out of range exception.
{code:sql}
SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL 292
DAYS)
{sql}
or
{code:sql}
SELECT CURRENT_TIME + INTERVAL 292 DAYS)
{sql}
Actual result
{noformat}
+10018-09-08T21:00:00Z
{noformat}
This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
ZONE).
> Sql. Adding interval to TIMESTAMP WITH LOCAL TIME ZONE doesn't check bounds
> ---
>
> Key: IGNITE-25154
> URL: https://issues.apache.org/jira/browse/IGNITE-25154
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> The following test must result in out of range exception.
> {code:sql}
> SELECT TIMESTAMP WITH LOCAL TIME ZONE '2024-01-01 00:00:00' + INTERVAL
> 292 DAYS)
> {code}
> or
> {code:sql}
> SELECT CURRENT_TIME + INTERVAL 292 DAYS)
> {code}
> Actual result
> {noformat}
> +10018-09-08T21:00:00Z
> {noformat}
> This does not reproduce with dynamic parameters and TIMESTAMP (WITHOUT TIME
> ZONE).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
