[MDEV-4441] DROP DATABASE with a newly created ARCHIVE table does not work Created: 2013-04-25  Updated: 2013-06-18  Resolved: 2013-06-18

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.2
Fix Version/s: 10.0.4

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-3808 Better table discovery Closed

 Description   

MariaDB [test]> CREATE TABLE t1 (i INT) ENGINE=ARCHIVE;
Query OK, 0 rows affected (0.01 sec)
 
MariaDB [test]> DROP DATABASE test;
ERROR 1010 (HY000): Error dropping database (can't rmdir './test', errno: 39 "Directory not empty")

I presume it has something to do with a lack of proper discovery on DROP DATABASE.
In previous versions the same scenario seems to work okay.

Test case:

--source include/have_archive.inc
 
CREATE TABLE t1 (i INT) ENGINE=ARCHIVE;
DROP DATABASE test;

revision-id: bar@mariadb.org-20130424142022-u4xhikvoqggze9b0
revno: 3745
branch-nick: 10.0



 Comments   
Comment by Sergei Golubchik [ 2013-06-18 ]

pushed in 10.0-base

Generated at Thu Feb 08 06:56:26 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.