You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Kalashnikov (JIRA)" <ji...@apache.org> on 2017/09/15 08:23:00 UTC
[jira] [Commented] (IGNITE-6349) SQL: Forbid NOT NULL constraints
usage for a cache with configured interceptor
[ https://issues.apache.org/jira/browse/IGNITE-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167519#comment-16167519 ]
Sergey Kalashnikov commented on IGNITE-6349:
--------------------------------------------
Implemented as part of <IGNITE-6350> as changes are very similar. PR is https://github.com/apache/ignite/pull/2656
> SQL: Forbid NOT NULL constraints usage for a cache with configured interceptor
> ------------------------------------------------------------------------------
>
> Key: IGNITE-6349
> URL: https://issues.apache.org/jira/browse/IGNITE-6349
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Sergey Kalashnikov
> Assignee: Sergey Kalashnikov
> Fix For: 2.3
>
>
> We need to throw an exception when user attempts to create or alter a table with a field declared as NOT NULL in a case the corresponding cache configuration employs cache interceptor {{CacheConfiguration.setInterceptor()}}.
> These features seem to not fit together quite well, so we skip the support at the moment and the check will keep things consistent.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)