You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Paschenko (JIRA)" <ji...@apache.org> on 2017/01/20 17:55:26 UTC

[jira] [Commented] (IGNITE-3595) Improve Enum fields handling in SQL.

    [ https://issues.apache.org/jira/browse/IGNITE-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832179#comment-15832179 ] 

Alexander Paschenko commented on IGNITE-3595:
---------------------------------------------

Optimization fix has been merged to H2, designing custom types support.

> Improve Enum fields handling in SQL.
> ------------------------------------
>
>                 Key: IGNITE-3595
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3595
>             Project: Ignite
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.7
>            Reporter: Sergi Vladykin
>            Assignee: Alexander Paschenko
>              Labels: important
>             Fix For: 1.9
>
>
> Currently queries like this do not work in Ignite if we use enum field on the left side and enum constant name or ordinal on the right side:
> select * from A where my_enum = 'ENUM_CONST';
> select * from A where my_enum = 3;
> This is a huge usability issue.
> We can try to solve it by contributing `User defined Value types` in H2 and implementing the special value type for Enums to handle comparison with String (convert to enum by name) and with int (convert to enum by ordinal).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)