[
https://issues.apache.org/jira/browse/IGNITE-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov resolved IGNITE-15926.
---------------------------------------
Resolution: Won't Fix
We don't need to provide separate method for every case. Mentioned
functionality could be achieved by simply catching an exception and ignoring
it, if needed.
> 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)
