Bug 1942526

Summary: DROP TABLE doesn't raise error while dropping non-existing table
Product: Red Hat Software Collections Reporter: Lukas Javorsky <ljavorsk>
Component: mariadbAssignee: Michal Schorm <mschorm>
Status: CLOSED CURRENTRELEASE QA Contact: Jakub Heger <jheger>
Severity: unspecified Docs Contact: Lenka Špačková <lkuprova>
Priority: unspecified    
Version: rh-mariadb105CC: databases-maint, mmuzila, pkubat
Target Milestone: alphaKeywords: Rebase, Triaged, ZStream
Target Release: 3.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
When the OQGraph storage engine plug-in is loaded to the MariaDB 10.5 server, MariaDB does not warn about dropping a non-existent table. In particular, when the user attempts to drop a non-existent table using the DROP TABLE or DROP TABLE IF EXISTS SQL commands, MariaDB neither returns an error message nor logs a warning. Note that the OQGraph plug-in is provided by the mariadb-oqgraph-engine package, which is not installed by default.
 Story Points: ---
Clone Of:
: 1944653 2101777 (view as bug list) Environment:
Last Closed: 2022-10-13 12:26:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2092347    
Bug Blocks: 1944653, 1947388, 2101777    

Description Lukas Javorsky 2021-03-24 13:58:55 UTC 
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): 
rh=mariadb105 (10.5.8-1)


How reproducible:
Always


Steps to Reproduce:
1. Install the rh-mariadb105 collection
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 'test.t'

Additional info:
NOTE: This bug is reproducible only on rh-mariadb105. Tested on mariadb-10.5.8 on Fedora-34, RHEL-8.5 and rh-mariadb103

2nd NOTE: It does raise an error when trying to DROP DATABASE on a non-existing database

There may be more issues we don't know about yet, so we need to fix this.
Comment 2 Lukas Javorsky 2021-03-31 10:17:08 UTC 
New updates (in BZ#1944653) about mariadb-oqgraph-engine show that, this subpackage is the one that is causing the issue.

I've tried to remove 'rh-mariadb105-mariadb-oqgraph-engine' and it really worked as expected.

This means we located the issue and now we can move to finding the actual problem that could cause this
Comment 3 Lukas Javorsky 2021-04-08 11:22:07 UTC 
The initial notes "It works on Fedora" are incorrect. I've tested this again and with the knowledge we have now, I've included the oqgraph-engine package and it causing the same issue there.

That's why I've created clone of this bug for Fedora OS -> BZ#1947388
Comment 4 Lukas Javorsky 2021-05-06 07:42:58 UTC 
Jira bug issue submitted: https://jira.mariadb.org/browse/MDEV-25373