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

LP:1006160 - View used via a trigger references old columns

    XMLWordPrintable

Details

    Description

      MariaDB 5.5.23 on Windows 32 bits tiggers following message in Windows application log:

      Slave SQL: Query caused different errors on master and slave. Error on master: message (format)='View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them' error code=1356 ; Error on slave: actual message='no error', error code=0. Default database: 'dbweilandt2'. Query: 'UPDATE vorgangsliste SET gerätestatusid = 4,gerätestatusid=4,garantie=NULL,`timestamp`= NOW() WHERE vorgangsnr = 190655', Error_code: 0

      Before that, a column name was changed (which usually triggers a "...references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights..." on views that use the old column name. At the time the above error was triggered, all views with reference to the changed column used the new column name. The only explanation is that somewhere in cache or Aria log file there was still the old name. "Vorgangsliste" is a table that triggers some views on update or on insert, but none of these triggers have references to the changed table.

      Table format is Aria.

      The only workaround to get the master working like it should was to stop and restart it.

      The master has been working for some weeks. Is there any chance to reproduce the problem?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nbrnhardt nbrnhardt (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.