[ 
https://issues.apache.org/jira/browse/IGNITE-25330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor updated IGNITE-25330:
--------------------------
    Description: 
*Steps to reproduce:*
{code:java}
[defaultNode]> sql
sql-cli> create zone if not exists "DEFAULT_ZONE" with 
storage_profiles='default'
Updated 0 rows.

sql-cli> create table 
eight_different_types_TINYINT_TIME_TIME_TINYINT_TINYINT_TIME_TIME_TINYINT(keyTINYINT0
 TINYINT not null, keyTIME1 TIME not null, keyTIME2 TIME not null, keyTINYINT3 
TINYINT not null, keyTINYINT4 TINYINT not null, keyTIME5 TIME not null, 
keyTIME6 TIME not null, keyTINYINT7 TINYINT not null, val INTEGER not null, 
primary key (keyTINYINT0, keyTIME1, keyTIME2, keyTINYINT3, keyTINYIN
T4, keyTIME5, keyTIME6, keyTINYINT7)) ZONE "DEFAULT_ZONE"
Updated 0 rows.

sql-cli> insert into 
eight_different_types_TINYINT_TIME_TIME_TINYINT_TINYINT_TIME_TIME_TINYINT(keyTINYINT0,
 keyTIME1, keyTIME2, keyTINYINT3, keyTINYINT4, keyTIME5, keyTIME6, keyTINYINT7, 
val) values (-90::TINYINT, '07:55:55'::TIME, '07:55:56'::TIME, -87::TINYINT, 
-86::TINYINT, '07:55:59'::TIME, '07:56'::TIME, -83::TINYINT, 116519::INTEGER)
SQL query execution error
Invalid TIME value, '07:56'
 {code}
*Extra info:*

The problem is reproduced since 01.05.2025.

  was:
*Steps to reproduce:*
{code:java}
[defaultNode]> sql
sql-cli> create zone if not exists "DEFAULT_ZONE" with 
storage_profiles='default'
Updated 0 rows.

sql-cli> create table 
eight_different_types_TINYINT_TIME_TIME_TINYINT_TINYINT_TIME_TIME_TINYINT(keyTINYINT0
 TINYINT not null, keyTIME1 TIME not null, keyTIME2 TIME not null, keyTINYINT3 
TINYINT not null, keyTINYINT4 TINYINT not null, keyTIME5 TIME not null, 
keyTIME6 TIME not null, keyTINYINT7 TINYINT not null, val INTEGER not null, 
primary key (keyTINYINT0, keyTIME1, keyTIME2, keyTINYINT3, keyTINYIN
T4, keyTIME5, keyTIME6, keyTINYINT7)) ZONE "DEFAULT_ZONE"
Updated 0 rows.

sql-cli> insert into 
eight_different_types_TINYINT_TIME_TIME_TINYINT_TINYINT_TIME_TIME_TINYINT(keyTINYINT0,
 keyTIME1, keyTIME2, keyTINYINT3, keyTINYINT4, keyTIME5, keyTIME6, keyTINYINT7, 
val) values (-90::TINYINT, '07:55:55'::TIME, '07:55:56'::TIME, -87::TINYINT, 
-86::TINYINT, '07:55:59'::TIME, '07:56'::TIME, -83::TINYINT, 116519::INTEGER)
SQL query execution error
Invalid TIME value, '07:56'
 {code}
*Extra info:*

Documentation says this syntax is supported: 
[https://www.gridgain.com/docs/gridgain9/latest/sql-reference/data-types#time]

The problem is reproduced since 01.05.2025.


> TIME datatype does not support hh:mm syntax while insert
> --------------------------------------------------------
>
>                 Key: IGNITE-25330
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25330
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 3.1
>            Reporter: Igor
>            Priority: Major
>              Labels: ignite-3
>
> *Steps to reproduce:*
> {code:java}
> [defaultNode]> sql
> sql-cli> create zone if not exists "DEFAULT_ZONE" with 
> storage_profiles='default'
> Updated 0 rows.
> sql-cli> create table 
> eight_different_types_TINYINT_TIME_TIME_TINYINT_TINYINT_TIME_TIME_TINYINT(keyTINYINT0
>  TINYINT not null, keyTIME1 TIME not null, keyTIME2 TIME not null, 
> keyTINYINT3 TINYINT not null, keyTINYINT4 TINYINT not null, keyTIME5 TIME not 
> null, keyTIME6 TIME not null, keyTINYINT7 TINYINT not null, val INTEGER not 
> null, primary key (keyTINYINT0, keyTIME1, keyTIME2, keyTINYINT3, keyTINYIN
> T4, keyTIME5, keyTIME6, keyTINYINT7)) ZONE "DEFAULT_ZONE"
> Updated 0 rows.
> sql-cli> insert into 
> eight_different_types_TINYINT_TIME_TIME_TINYINT_TINYINT_TIME_TIME_TINYINT(keyTINYINT0,
>  keyTIME1, keyTIME2, keyTINYINT3, keyTINYINT4, keyTIME5, keyTIME6, 
> keyTINYINT7, val) values (-90::TINYINT, '07:55:55'::TIME, '07:55:56'::TIME, 
> -87::TINYINT, -86::TINYINT, '07:55:59'::TIME, '07:56'::TIME, -83::TINYINT, 
> 116519::INTEGER)
> SQL query execution error
> Invalid TIME value, '07:56'
>  {code}
> *Extra info:*
> The problem is reproduced since 01.05.2025.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to