[
https://issues.apache.org/jira/browse/IGNITE-20728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-20728:
---------------------------------------
Epic Link: IGNITE-20729
> Sql. improve test coverage for UUID data type
> ---------------------------------------------
>
> Key: IGNITE-20728
> URL: https://issues.apache.org/jira/browse/IGNITE-20728
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Priority: Major
> Labels: ignite-3
>
> AI3 have not enough test coverege for UUID data type.
> Let's add at least the following:
> 1. on basic expression for NOT BETWEEN (as an example need to take
> org.apache.ignite.internal.sql.engine.datatypes.tests.BaseExpressionDataTypeTest#testBetweenWithDynamicParameters
> / testBetweenWithLiterals )
> 2. Arithmetic operators, string concatenation operators, and other operators
> or functions that are not defined on values of UUID data type, should not be
> permitted.
> 3. We have tests for aggregation functions *count, min, max, any_value, some,
> GROUP BY, HAVING*. Other aggregate functions should not be permitted for UUID
> 4. Drop an index, check that data is accessible via scan.
> 5. Set operations between UUID data type and character types are not legal,
> because set operations are allowed only between compatible types. (e.g.
> expected error for *SELECT 'aaaaa' UNION SELECT '1111-1111-1111-1111'::UUID* )
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
