You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2021/12/10 16:10:00 UTC

[jira] [Commented] (IGNITE-15926) Implement two methods for dropping a table for the table existing and not

    [ https://issues.apache.org/jira/browse/IGNITE-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457237#comment-17457237 ] 

Evgeny Stanilovsky commented on IGNITE-15926:
---------------------------------------------

I suppose it resolved erroneously, correct exception not thrown. Plz reopen it?
I can call more that once tableManager.dropTable("TBL_NAME") and no exception thrown, also a can call it with not existing table, and no exception will be raised. 

> Implement two methods for dropping a table for the table existing and not
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-15926
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15926
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> ANSI standard requires two methods for dropping table for the two DDL:
> _DROP TABLE [ IF EXISTS ] syntax_
> for the purpose, Table manager should provide two methods with similar semantic.
> {code}
> TableManager#dropTable(String) throws TableNotExists
> TableManager#dropTableIfExists(String)
> {code}
> Also we need to support [1] ALTER TABLE [ IF EXISTS ] [ADD|DROP|ALTER] COLUMN
> [1] https://postgrespro.ru/docs/postgrespro/9.6/sql-altertable



--
This message was sent by Atlassian Jira
(v8.20.1#820001)