You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Iurii Gerzhedovich (Jira)" <ji...@apache.org> on 2024/02/12 15:02:00 UTC
[jira] [Updated] (IGNITE-21518) Sql. Improve test coverage for DDL
[ https://issues.apache.org/jira/browse/IGNITE-21518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Iurii Gerzhedovich updated IGNITE-21518:
----------------------------------------
Epic Link: IGNITE-20729
> Sql. Improve test coverage for DDL
> ----------------------------------
>
> Key: IGNITE-21518
> URL: https://issues.apache.org/jira/browse/IGNITE-21518
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Iurii Gerzhedovich
> Priority: Major
> Labels: ignite-3
>
> During implementation of DDLÂ were added set of tests. However added set of tests is insufficient.
> Let's add the following test scenarios:
> h4. Unit Testing:
> * Tests for SQL parser required additional test to for each DDL command, every option, every data type. Partial already covered, but not for all data types
> * Tests for components that handle DDL commands: test case each DDL command, every option, every data type. Partialy already covered, but not for all data types.
> h4. Functional and E2E tests:
> TABLE:
> * Effects of DDL operations should be observable via all access API. Partialy already covered, but not for all combinations of data type and API access type.
> * check that it is possible to perform operations against a newly created table via all available APIs.
> * check that primary key columns are not modifiable (no SQL tests).
> DEFAULTS:
> * check that a column is set to a value equal to DEFAULT, if the DEFAULT keyword is used in insert operation instead of a value (not all types are covered right now).
> * check that it is not allowed to set a value of another type as DEFAULT value (some types are not covered).
> * check that a value specified as DEFAULT lies in the domain of values for that data type.
> * check that DEFAULT does not support expressions - only literals and function names.
> * check that null constraint makes columns nullable.
> * check that DROP DEFAULT is supported.
> INDEX:
> * check that if an index type is not specified (via USING clause), a tree (sorted) index is created.
> * Sorted/Tree index should support NULLS FIRST, NULLS LAST options for both ASC and DESC orderings.
> * check that after an index is dropped plans that previously used an index no longer use such index.
> TRANSACTIONS:
> * execution of a DDL operation via JDBC Connection with auto-commit flag set to false return an error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)