[
https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470012#comment-16470012
]
Vladimir Ozerov commented on IGNITE-6055:
-----------------------------------------
[~NIzhikov], my comments:
1) I do not see a case when existing data should be truncated. Data created on
previous versions should be treated as {{VARCHAR(MAX)}}. And we do not support
{{ALTER COLUMN}} at the moment. Am I missing something?
2) Yes, length constraints should be configurable inside {{QueryEntity}} and
{{QuerySqlField}}. It should be done in the same ticket IMO, as this is
integral part of our API.
> 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
>
> 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)
