You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Chenjian (Jira)" <ji...@apache.org> on 2022/12/13 07:48:00 UTC

[jira] [Created] (IGNITE-18388) Ignite drop then add same column has the wrong sematic

Chenjian created IGNITE-18388:
---------------------------------

             Summary: Ignite drop then add same column has the wrong sematic 
                 Key: IGNITE-18388
                 URL: https://issues.apache.org/jira/browse/IGNITE-18388
             Project: Ignite
          Issue Type: Bug
          Components: sql
    Affects Versions: 2.14, 2.13, 2.12, 2.11, 2.10, 2.9, 2.8
            Reporter: Chenjian
         Attachments: image-2022-12-13-15-43-58-095.png

Dropped the column then added the column with the same name, the value about the column backend which should not.

Steps to reproduce:
 * create table t(id int primary key, x int, y int)
 * insert into t values (1, 2, 3)
 * select * from t. The result shows as expected 1, 2, 3
 * alter table drop column x.
 * select * from t. The result shows as expected 1,3
 * alter table add column x int. 
 * select * from t. *The result shows NOT as expected 1,3,2. which should 1,3,NULL.*

 

!image-2022-12-13-15-43-58-095.png!



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