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

A view can mask a table that supports discovery

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.6
    • 10.0.7
    • None
    • None

    Description

      CREATE TABLE t1 (i INT) ENGINE=TokuDB;
      		 
      CREATE VIEW t1 AS SELECT "I am a view" AS a;
      		 
       
      		 
      SELECT * FROM t1;
      		 

      SELECT * FROM t1;
      		 
      a
      		 
      I am a view

      Not reproducible with MyISAM or InnoDB:

      CREATE TABLE t1 (i INT) ENGINE=MyISAM;
      		 
      CREATE VIEW t1 AS SELECT "I am a view" AS a;
      		 
      bug.t3_tokudb                            [ fail ]
      		 
              Test ended at 2013-12-13 00:46:34
      		 
       
      		 
      CURRENT_TEST: bug.t3_tokudb
      		 
      mysqltest: At line 2: query 'CREATE VIEW t1 AS SELECT "I am a view" AS a' failed: 1050: Table 't1' already exists

      Not reproducible on 5.5.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          serg Sergei Golubchik added a comment -

          Same with Archive. Or — I suppose — any engine that supports table discovery.

          serg Sergei Golubchik added a comment - Same with Archive. Or — I suppose — any engine that supports table discovery.
          elenst Elena Stepanova added a comment -

          Indeed, I did not consider that TokuDB is different from lets say InnoDB in terms of table discovery.
          I've modified the summary.

          It is a problem also because it can easily cause replication failure. If I add, for example, "SELECT * FROM t1" after table creation, then the view creation fails as expected; but in case of replication, only two CREATE statements will be replicated (the latter with the error code), while SELECT won't be in the binlog, so on slave the second CREATE will pass, which will cause different error codes on master and slave, which means replication failure.

          elenst Elena Stepanova added a comment - Indeed, I did not consider that TokuDB is different from lets say InnoDB in terms of table discovery. I've modified the summary. It is a problem also because it can easily cause replication failure. If I add, for example, "SELECT * FROM t1" after table creation, then the view creation fails as expected; but in case of replication, only two CREATE statements will be replicated (the latter with the error code), while SELECT won't be in the binlog, so on slave the second CREATE will pass, which will cause different error codes on master and slave, which means replication failure.

          People

            serg Sergei Golubchik
            elenst Elena Stepanova
            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.