ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-6293) SQL: Support FOREIGN KEY constraint
Date Thu, 14 Feb 2019 15:18:01 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vladimir Ozerov closed IGNITE-6293.

> SQL: Support FOREIGN KEY constraint
> -----------------------------------
>                 Key: IGNITE-6293
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6293
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>            Priority: Major
>              Labels: sql-engine
> We need to support {{FOREIGN KEY}} constraint. This is a complex, though achievable thing.
> 1) We need to check constraint during inserts and updates (from both SQL and cache API).

> 2) We need to support different modes of {{CASCADE}} actions - "remove", "set null".

> In general case it would require distributed operations, possibly with predicates. However,
as a first iteration, it would be enough to support FK only for co-located data. In this case
everything could be done locally.
> *Important* 
> Implementation of FK typically depends heavily on underlying MVCC and transaction subsystems.
That said, we should implement it after MVCC and transactional SQL.

This message was sent by Atlassian JIRA

View raw message