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

sys.create_synonym_db fails with ER_VIEW_SELECT_TMPTABLE when schema contains temporary tables

    XMLWordPrintable

Details

    Description

      Previous versions have a corner-case problem, sys.create_synonym_db cannot work when a temporary table overshadows a base table with the same name (MDEV-28342).

      However, MDEV-12459 extends it to any schema which contains a temporary table, even without overshadowing. This is a regression.

      create database db;
      		 
      use db;
      		 
      create table t (b int);
      		 
      create temporary table tmp (a int);
      		 
       
      		 
      call sys.create_synonym_db('db','db_syn');

      preview-10.9-MDEV-20119-misc c906db303

      		 
      mysqltest: At line 6: query 'call sys.create_synonym_db('db','db_syn')' failed: ER_VIEW_SELECT_TMPTABLE (1352): View's SELECT refers to a temporary table 'tmp'

      Attachments

        Issue Links

          is caused by

          Task - A task that needs to be done. MDEV-12459 The information_schema tables for getting temporary tables info is missing, at least for innodb there is no INNODB_TEMP_TABLE_INFO

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28342 sys.create_synonym_db fails when a temporary table masks a base table

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              anel Anel Husakovic
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.