You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2024/05/08 12:06:00 UTC

[jira] [Assigned] (IGNITE-22135) Sql. Investigate get ride support of CHAR datatype.

     [ https://issues.apache.org/jira/browse/IGNITE-22135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Orlov reassigned IGNITE-22135:
-----------------------------------------

    Assignee: Konstantin Orlov

> Sql. Investigate get ride support of CHAR datatype.
> ---------------------------------------------------
>
>                 Key: IGNITE-22135
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22135
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Iurii Gerzhedovich
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> CHAR type is not widely used by users, however, the type has specific need to be supported and requires significant time to do it right.
> Let's consider the ability to get rid of the type.
> List possibility solutions ordered by priority:
> 1. Make CHAR type an alias for VARCHAR, but take into account that in the future we can start supporting the type in the right way and need to be sure we can support smooth migration from the version that does not support CHAR to the new one with such support ( as example - metadata for such type should reflect real type VARCHAR)
> 2. Forbid CHAR type at all. No alias even.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)