Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.5.19
-
None
-
Linux Debian 11.7
Description
Stored generated columns depending on other columns:
- are properly updated after these other columns get updated by a simple "UPDATE" statement;
- are NOT updated after these other columns get updated by a "CASCADE" operation caused by a foreign key constraint.
The latter is apparently a bug. With a table with almost 2300 rows, after several updates caused by "cascade" foreign key constraints which I don't even remember, I am left with no other option than to remove the generated columns and add them again - in order to make MariaDB notice the changes in foreign keys. IMO it shouldn't be so.
Attachments
Issue Links
- duplicates
-
MDEV-18114 Foreign Key Constraint actions don't affect Virtual Column
- Closed