Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-31434

stored generated columns are not properly updated after update

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.5.19
    • N/A
    • Virtual Columns
    • 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

          Activity

            People

              serg Sergei Golubchik
              piotrniz Piotr Nizynski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.