Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
Description
If a field is a part of a foreign key with a ON UPDATE CASCADE action, it can be updated internally by InnoDB without informing the server and without validating the CHECK constraint. In other words, such cascading updates can invalidate the constraint and that's why they are not supported since MDEV-30606.
It was stated that It's possible to implement CHECK constraint validation on cascading updates, hence this task to do this in version 11.1+ at least.
Attachments
Issue Links
- duplicates
-
MDEV-22880 Honor constraints on UPDATE CASCADE
- Open
- is blocked by
-
MDEV-12302 Execute triggers for foreign key updates/deletes
- Confirmed
- relates to
-
MDEV-18114 Foreign Key Constraint actions don't affect Virtual Column
- Closed
-
MDEV-22602 WITHOUT OVERLAPS constraint is ignored when update is performed via foreign key cascade
- Closed
-
MDEV-29181 Potential corruption on Foreign key update on a table with vcol index
- Stalled
-
MDEV-30606 Foreign key cannot be used in the check constraint
- Closed