[jira] [Updated] (IGNITE-10471) SQL: Alter table to add column syntax doesn't support the user types but drop column can drop such fields

["Stanislav Lukyanov (JIRA)" <ji...@apache.org>]

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

Stanislav Lukyanov updated IGNITE-10471:
----------------------------------------
    Summary: SQL: Alter table to add column syntax doesn't support the user types but drop column can drop such fields  (was: SQL: Alter table to add column sytax doesn't support the user types but drop column can drop such fields)

> SQL: Alter table to add column syntax doesn't support the user types but drop column can drop such fields
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10471
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10471
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.6
>            Reporter: Andrey Aleksandrov
>            Priority: Minor
>             Fix For: 2.8
>
>
> Looks like ALTER COLUMN commands could be used only on a subset of supported types (that could be used in CREATE TABLE syntax):
> [https://apacheignite-sql.readme.io/docs/data-types]
> But using query entities we can provide to use a field that has user types.
> This fields can be used in 
> ALTER TABLE CACHE_NAME DROP COLUMN COLUMN_NAME
> But it can't be used as next:
> ALTER TABLE CACHE_NAME  ADD COLUMN COLUMN_NAME 'type'
> Where type is a user's one.
> Possible we should think about supporting POJO and enums.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)