Vladimir Ozerov created IGNITE-6293:
---------------------------------------
Summary: 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
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
(v6.4.14#64029)
