Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.3.11, 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
-
CentOS 7
Description
One of my tables has several columns with FK ON DELETE SET NULL constraints on them, plus one virtual column with mildly complex expression based on these FK columns.
When a DELETE is issued on the foreign table, the FK fields get set to NULL but the STORED Virtual column is not updated.
There is no trace of this behaviour on the documentation.
Attachments
Issue Links
- causes
-
MDEV-31931 FK fields cannot be used anymore in generated columns
- Closed
-
MDEV-32030 Error in restoring SQL dump with virtual columns after upgrade to version 10.6.15
- Closed
- includes
-
MDEV-31322 FKs with 'ON UPDATE CASCADE' can be set in some contexts but not others
- Closed
-
MDEV-32764 Segmentation fault at /mariadb-11.3.0/strings/ctype-utf8.c:831
- Closed
- is duplicated by
-
MDEV-31434 stored generated columns are not properly updated after update
- Closed
- relates to
-
MDEV-22602 WITHOUT OVERLAPS constraint is ignored when update is performed via foreign key cascade
- Closed
-
MDEV-30674 Implement CHECK constraints validation on cascading updates
- Closed
-
MDEV-31654 Support STORED generated columns with FK cascade changes
- Open
-
MDEV-31112 vcol circular references lead to stack overflow
- Closed