[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 Created: 2021-04-08  Updated: 2022-01-17  Resolved: 2022-01-17

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - OQGRAPH
Affects Version/s: 10.5
Fix Version/s: 10.5.14, 10.6.6

Type: Bug Priority: Critical
Reporter: Lukas Javorsky Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None
Environment:

Fedora, RHEL, CentOS

Issue Links:
Relates
relates to MDEV-11412 Ensure that table is truly dropped wh... Closed

 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

 Comments   
Comment by Marko Mäkelä [ 2021-04-08 ]

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

Comment by Michal Schorm [ 2021-04-08 ]

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.

Comment by Sergei Golubchik [ 2021-04-09 ]

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

Generated at Thu Feb 08 09:37:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.