[
https://issues.apache.org/jira/browse/IGNITE-19481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-19481:
--------------------------------------
Labels: calcite2-required ignite-3 (was: ignite-3)
> Sql. Inconsistent behaviour of DML operations introduced by implicit type
> casts.
> --------------------------------------------------------------------------------
>
> Key: IGNITE-19481
> URL: https://issues.apache.org/jira/browse/IGNITE-19481
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Maksim Zhuravkov
> Priority: Minor
> Labels: calcite2-required, ignite-3
>
> INSERT:
> {code:java}
> @Test
> public void testInsertIntToStr() {
> sql("CREATE TABLE t1(int_col INTEGER PRIMARY KEY, str_col VARCHAR)");
> sql("INSERT INTO t1 VALUES(1, 2)");
> }
> {code}
> Result: OK
> UPDATE:
> {code:java}
> @Test
> public void testUpdateIntToStr() {
> sql("CREATE TABLE t1(int_col INTEGER PRIMARY KEY, str_col VARCHAR)");
> sql("INSERT INTO t1 VALUES(1, '11111')");
> sql("UPDATE t1 SET str_col=1");
> }
> {code}
> Error:
> {code:java}
> TraceId:3b57d830-a327-4c77-89ec-a45a1411daf6 class java.lang.Integer cannot
> be cast to class java.lang.String (java.lang.Integer and java.lang.String are
> in module java.base of loader 'bootstrap')
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)