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

DROP TABLE doesn't raise error while dropping non-existing table in MariaDB 10.5.9 when OQGraph SE is loaded to the server

Details

    Description

      Description of problem:
      The MariaDB doesn't raise an error while trying to drop a non-existing table.

      Version-Release number of selected component (if applicable):
      mariadb-10.5-*

      How reproducible:
      Always

      Steps to Reproduce:
      1. Install the mariadb-server mariadb mariadb-oqgraph-engine
      2. Start the server
      3. Create a database
      4. Create a table
      5. Drop the table
      6. Drop the same table again (it will not fail, but it should)

      Actual results:
      Doesn't raise an error

      Expected results:
      Should raise error while dropping non-existing table (step 6)
      Error: ERROR 1051 (42S02): Unknown table 'database.table'

      I've also tested the RPMs you have in this repo (http://yum.mariadb.org/10.5/fedora/33/x86_64/) and it is still failing.

      This bug exists only in MariaDB version > 10.4

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-11412 Ensure that table is truly dropped when using DROP TABLE

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

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment -

            Is this really a bug, or an intended consequence of MDEV-11412?

            marko Marko Mäkelä added a comment - Is this really a bug, or an intended consequence of MDEV-11412 ?
            mschorm Michal Schorm added a comment -

            When "IF EXISTS" clause is added to "DROP TABLE", it always logs warning and errors.
            I would expect to see a warning that I tried to drop non-existing table.

            —

            Intended change or not - why the behaviour differs only when OQGraph SE is loaded to the DB server ?
            Even when loaded at runtime, the behaviour will switch to "no warnings / no errors raised", when OQGraph unloaded at runtime again, it will switch to the original behaviour.

            mschorm Michal Schorm added a comment - When "IF EXISTS" clause is added to "DROP TABLE", it always logs warning and errors. I would expect to see a warning that I tried to drop non-existing table. — Intended change or not - why the behaviour differs only when OQGraph SE is loaded to the DB server ? Even when loaded at runtime, the behaviour will switch to "no warnings / no errors raised", when OQGraph unloaded at runtime again, it will switch to the original behaviour.
            serg Sergei Golubchik added a comment -

            marko, I suspect it's unintented consequence of MDEV-11412

            serg Sergei Golubchik added a comment - marko , I suspect it's unintented consequence of MDEV-11412

            People

              serg Sergei Golubchik
              ljavorsk Lukas Javorsky
              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.