[MDEV-31434] stored generated columns are not properly updated after update Created: 2023-06-08  Updated: 2023-06-29  Resolved: 2023-06-29

Status: Closed
Project: MariaDB Server
Component/s: Virtual Columns
Affects Version/s: 10.5.19
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Piotr Nizynski Assignee: Sergei Golubchik
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Linux Debian 11.7

Issue Links:
Duplicate
duplicates MDEV-18114 Foreign Key Constraint actions don't ... Closed

 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.

 Comments   
Comment by Sergei Golubchik [ 2023-06-29 ]

Thanks! It'll be fixed in MDEV-18114.

Generated at Thu Feb 08 10:23:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.