You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2023/10/10 08:42:00 UTC
[jira] [Updated] (IGNITE-20593) Sql. Add implicit cast coercion rules to DdlSqlToCommandConverter.
[ https://issues.apache.org/jira/browse/IGNITE-20593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Zhuravkov updated IGNITE-20593:
--------------------------------------
Description:
In order to make behaviour of types in DDL commands consistent with other SQL statements, we need to update `DdlSqlToCommandConverter` to make it in sync with implicit type coercion rules
- if type T1 can be converted from T2, then DEFAULT for type T1 can accept values of type T2.
was:
At the moment it is not possible to specify a value for default column of UUID data type. The following error is returned - Unknown type [type=UUID].
We can fix this error by allowing to set a varchar value in default constraint from UUID data type (because a varchar can be implicitly converted to UUID).
Summary: Sql. Add implicit cast coercion rules to DdlSqlToCommandConverter. (was: Sql. Attempting to specify default value for UUID column results in "Unknown type [type=UUID]")
> Sql. Add implicit cast coercion rules to DdlSqlToCommandConverter.
> ------------------------------------------------------------------
>
> Key: IGNITE-20593
> URL: https://issues.apache.org/jira/browse/IGNITE-20593
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Maksim Zhuravkov
> Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> In order to make behaviour of types in DDL commands consistent with other SQL statements, we need to update `DdlSqlToCommandConverter` to make it in sync with implicit type coercion rules
> - if type T1 can be converted from T2, then DEFAULT for type T1 can accept values of type T2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)