[
https://issues.apache.org/jira/browse/IGNITE-24022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-24022:
--------------------------------------
Description:
As for now, we already have CreateSchemaCommand - a Catalog command for
creating schemas.
It is used for creating the SYSTEM schema, but doesn't serve user schemas
creation commands.
Let's revisit the command's code, fix it and add tests.
1. The command must respect reserved schema-names like. These schemas must
never be deleted/renamed or created by the user, even if we don't assumed
supporting them in future.
Reserved schema names are:
* SYSTEM - it is used and created by Ignite itself for internal needs.
* INFORMATION_SCHEMA - as defined in SQL standard.
* DEFINITION_SCHEMA - as defined in SQL standard.
2. Add tests for schema name uniqueness.
was:
As for now, we already have a Catalog command for creating schemas.
It is used for creating the SYSTEM schema, but doesn't serve user schemas
creation commands.
Let's revisit the command's code, fix it and add tests.
1. The command must respect reserved schema-names like. These schemas must
never be deleted/renamed or created by the user, even if we don't assumed
supporting them in future.
Reserved schema names are:
* SYSTEM - it is used and created by Ignite itself for internal needs.
* INFORMATION_SCHEMA - as defined in SQL standard.
* DEFINITION_SCHEMA - as defined in SQL standard.
2. Add tests for schema name uniqueness.
> Sql. Fix CreateSchemaCommand catalog command validation.
> --------------------------------------------------------
>
> Key: IGNITE-24022
> URL: https://issues.apache.org/jira/browse/IGNITE-24022
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
>
> As for now, we already have CreateSchemaCommand - a Catalog command for
> creating schemas.
> It is used for creating the SYSTEM schema, but doesn't serve user schemas
> creation commands.
> Let's revisit the command's code, fix it and add tests.
> 1. The command must respect reserved schema-names like. These schemas must
> never be deleted/renamed or created by the user, even if we don't assumed
> supporting them in future.
> Reserved schema names are:
> * SYSTEM - it is used and created by Ignite itself for internal needs.
> * INFORMATION_SCHEMA - as defined in SQL standard.
> * DEFINITION_SCHEMA - as defined in SQL standard.
> 2. Add tests for schema name uniqueness.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
