[MDEV-32505] Spider: DROP TABLE succeeds where it should not Created: 2023-10-18  Updated: 2023-10-18  Resolved: 2023-10-18

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Spider
Affects Version/s: 10.5, 10.6, 10.9, 10.10, 10.11, 11.0, 11.1, 11.2, 11.3
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Roel Van de Paar Assignee: Yuchen Pei
Resolution: Duplicate Votes: 0
Labels: corruption, regression-10.5

Issue Links:
Duplicate
duplicates MDEV-30170 no error for DROP TABLE and no warnin... Closed
Relates

 Description   

INSTALL PLUGIN Spider SONAME 'ha_spider.so';
--error ER_BAD_TABLE_ERROR
DROP TABLE t1;

Leads to:

10.5.23 6b343de8ef51e4c92f0ea2bf62f27f0aab32204d (Debug)

CURRENT_TEST: main.test
mysqltest: At line 3: query 'DROP TABLE t1' succeeded - should have failed with errno 1051...

The DROP TABLE t1 should fail (and thus the MTR testcase should succeed as --error ER_BAD_TABLE_ERROR was specified). However, it succeeds. There are possibly other more serious variations/implications of this scenario. If a code check shows that the issue is limited to an incorrect "Query OK" return only, the priority can be lowered.



 Comments   
Comment by Roel Van de Paar [ 2023-10-18 ]

Possible cause MDEV-11412?

Comment by Yuchen Pei [ 2023-10-18 ]

Duplicate of MDEV-30170

Generated at Thu Feb 08 10:31:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.