[MDEV-23549] CREATE fails after DROP without FRM Created: 2020-08-23  Updated: 2020-10-06  Resolved: 2020-09-07

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.5
Fix Version/s: 10.5.7

Type: Bug Priority: Critical
Reporter: Aleksey Midenkov Assignee: Aleksey Midenkov
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-16417 Store Foreign Key metadata outside of... In Review
Problem/Incident
is caused by MDEV-11412 Ensure that table is truly dropped wh... Closed

 Description   

Reproduce

--source include/have_innodb.inc
--let $DATADIR= `select @@datadir`
 
create table parent (id int not null, primary key (id)) engine=innodb;
select * from parent;
--remove_file $datadir/test/parent.frm
 
drop table parent;
create table parent (id int not null, primary key (id)) engine=innodb;
 
# Cleanup
drop table parent;

Result

mysqltest: At line 9: query 'create table parent (id int not null, primary key (id)) engine=innodb' failed: 1050: Table 'parent' already exists

Related tests

main.drop_table_force



 Comments   
Comment by Oleksandr Byelkin [ 2020-08-25 ]

https://github.com/MariaDB/server/commit/1c4ecdfd39826d7850300570d912e6523157d760

Comment by Oleksandr Byelkin [ 2020-08-27 ]

OK to push

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