[
https://issues.apache.org/jira/browse/IGNITE-24025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-24025:
--------------------------------------
Fix Version/s: 3.0
> Sql. Introduce drop schema catalog command
> ------------------------------------------
>
> Key: IGNITE-24025
> URL: https://issues.apache.org/jira/browse/IGNITE-24025
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> In order to handle SQL statements like
> {noformat}
> DROP SCHEMA [IF EXISTS] <schema name identifier> [CASCADE | RESTRICT];
> {noformat}
> We need to introduce DropSchemaCatalogCommand.
> CASCADE drop behavior forces dropping all its objects together with the
> schema at once.
> RESTRICT drop behavior drops schema if empty or fails otherwise.
> Default behavior: RESTRICT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
