weird drop innodb table with skip-innodb

I think while some engine is not runnig DDL, DML or any other commands
shouldn't be executed against it at all! Then how come...

System:
Microsoft Windows 2000
5.00.2195
Service Pack 4
P4 2.4GHz 512Mb RAM
mysql Ver 14.12 Distrib 5.0.17, for Win32 (ia32)
innodb_file_per_table

Simple test case:
1. start mysql with:
#skip-innodb
innodb_file_per_table
2.
mysql> create database test;
Query OK, 1 row affected (0.02 sec)
mysql> use test;
Database changed
mysql> create table customers(a int, b char(16)) Engine=INNODB;
Query OK, 0 rows affected (0.13 sec)

mysql> insert into customers Values(1, 'a1');
Query OK, 1 row affected (0.03 sec)
// actually there could be *important data* in it! table/dir ...\test:
//customers.frm
//customers.ibd
//db.opt
3. stop mysql then start with skip-innodb and reconnect
4. At this point innodb is not runnig! Try Drop some innodb table(s):
mysql> drop table test.customers;
ERROR 6 (HY000): Error on delete of '.\test\customers.MYI' (Errcode: 2)
// fires too late - customers.frm *already DELETED*

I think this *shouldn't* happen while (innodb in this case) engine is
*NOT Running* (I know I can recreate .frm file yet... accidents happen,
and what if I dont have that table definition at hand :()

HTH ...and still waiting for solution

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org