[
https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586045#comment-16586045
]
Nikolay Izhikov edited comment on IGNITE-6055 at 8/20/18 2:54 PM:
------------------------------------------------------------------
[~isapego]
> What was done for other clients? Only configuration was changed?
1. Java, .Net - support of new Fields in QueryEntity was added. Backward
compatibility is preserved.
2. NodeJs - protocol version is updated.
3. JDBC - information of field precision(VARCHAR maximum length) added to
column metadata.
was (Author: nizhikov):
> What was done for other clients? Only configuration was changed?
1. Java, .Net - support of new Fields in QueryEntity was added. Backward
compatibility is preserved.
2. NodeJs - protocol version is updated.
3. JDBC - information of field precision(VARCHAR maximum length) added to
column metadata.
> SQL: Add String length constraint
> ---------------------------------
>
> Key: IGNITE-6055
> URL: https://issues.apache.org/jira/browse/IGNITE-6055
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.1
> Reporter: Vladimir Ozerov
> Assignee: Nikolay Izhikov
> Priority: Major
> Labels: sql-engine
> Fix For: 2.7
>
>
> We should support {{CHAR(X)}} and {{VARCHAR{X}} syntax. Currently, we ignore
> it. First, it affects semantics. E.g., one can insert a string with greater
> length into a cache/table without any problems. Second, it limits efficiency
> of our default configuration. E.g., index inline cannot be applied to
> {{String}} data type as we cannot guess it's length.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
