You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/07/03 07:25:00 UTC
[jira] [Commented] (IGNITE-19644) Drop 'COLUMN IF (NOT) EXISTS' syntax support.
[ https://issues.apache.org/jira/browse/IGNITE-19644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739471#comment-17739471 ]
Konstantin Orlov commented on IGNITE-19644:
-------------------------------------------
[~zstan], as I see, you removed "Docs Required" flag. May you elaborate, why we don't need to update documentation accordingly?
> Drop 'COLUMN IF (NOT) EXISTS' syntax support.
> ---------------------------------------------
>
> Key: IGNITE-19644
> URL: https://issues.apache.org/jira/browse/IGNITE-19644
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Andrey Mashenkov
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3, tech-debt
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Let's drop supporting ambiguous "COLUMN IF (NOT) EXISTS" syntax.
> Motivation.
> "IF EXISTS/IF NOT EXISTS" clause is not a part of SQL standard.
> It usage looks ambiguous when statement contains multiple actions for adding/dropping multiple columns. Multiple actions support is desirable due to performance reasons.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)