You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Daschinskiy (JIRA)" <ji...@apache.org> on 2018/08/03 13:44:00 UTC
[jira] [Comment Edited] (IGNITE-9183) Proper handling UUID columns,
that are added by DDL.
[ https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568219#comment-16568219 ]
Ivan Daschinskiy edited comment on IGNITE-9183 at 8/3/18 1:43 PM:
------------------------------------------------------------------
[Pull Request #4483|https://github.com/apache/ignite/pull/4483]
was (Author: ivandasch):
[Pull Request|https://github.com/apache/ignite/pull/4483]
> Proper handling UUID columns, that are added by DDL.
> ----------------------------------------------------
>
> Key: IGNITE-9183
> URL: https://issues.apache.org/jira/browse/IGNITE-9183
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.5, 2.6
> Reporter: Ivan Daschinskiy
> Assignee: Ivan Daschinskiy
> Priority: Major
> Fix For: 2.7
>
>
> Currently, if we added new UUID columnt thru DDL, it is saved to schema as byte[]. So it's impossible to use it with DML without placeholders and put values thru cache api without converting UUID to byte[].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)