ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Kalashnikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5648) DDL: NOT NULL constraint support for CREATE TABLE operator
Date Tue, 12 Sep 2017 07:52:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162634#comment-16162634

Sergey Kalashnikov commented on IGNITE-5648:

[~sboikov], [~vozerov],
Points 1, 2 - fixed. However, I skipped the parts related to cache interceptor and other infrequently
used facilities for now. We discussed this with Vova and decided to address this in separate
tickets (in fact, we want to forbid using NOT_NULL fields when a cache has interceptor/read-through/conflict
resolver configured).
Point 3 - It is only possible to create index on a cache that already have QueryEntity configured.
So, I think the way GridCacheContext.isQueryEnabled() implemented is ok (at least for the
time being).

> DDL: NOT NULL constraint support for CREATE TABLE operator
> ----------------------------------------------------------
>                 Key: IGNITE-5648
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5648
>             Project: Ignite
>          Issue Type: New Feature
>          Components: sql
>    Affects Versions: 2.0
>            Reporter: Denis Magda
>            Assignee: Sergey Kalashnikov
>             Fix For: 2.3
> This is an umbrella ticket intended to aggregate all the activities related to {{NOT
NULL}} constraint support for {{CREATE TABLE}} commands.
> {code}
> {code}
> Ignite must prevent setting {{legid}} to {{null}} value.
> The feature has to be supported for:
> * ODBC and JDBC drivers.
> * Native APIs (Java, .NET, C++)

This message was sent by Atlassian JIRA

View raw message