[
https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523251#comment-16523251
]
Nikolay Izhikov commented on IGNITE-6055:
-----------------------------------------
I've checked out "Review checklist" [1]
Here are compatibility rules:
{noformat}
Compatibility
1. Persistence backward compatibility MUST be maintained between minor
releases. It should be possible to start newer version on data files created by
the previous version
2. Thin client forward and backward compatibility SHOULD be maintained
between two consecutive minor releases. If compatibility cannot be maintained
it MUST be described in "Migration Guide" [2]
3. JDBC and ODBC forward and backward compatibility SHOULD be maintained
between two consecutive minor releases. If compatibility cannot be maintained
it MUST be described in "Migration Guide" [2]
{noformat}
There is nothing about .Net compatibility.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Review+Checklist
> 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)
