Bug #8625 Can't create INO DB table with a specific name anymore (errno: 150)
Submitted: 19 Feb 2005 12:36 Modified: 19 Feb 2005 12:58
Reporter: Alex Curvers Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:4.0.23 OS:pc-linux-gnu (i386)
Assigned to: CPU Architecture:Any

[19 Feb 2005 12:36] Alex Curvers
Description:
I made a ino db table named vendorinvoicerules and added a foreign key constraint to vendorinvoices on a varchar field. The foreign key constraint was not working as expected (or not atall) so to try to fix it i dropped both tables and recreated them dropped and recreated the indexes.  When i got to the point where i wanted to convert the new vendorinvoicerules table from myisam to ino db it failed with:
Can't create table './gshnew/vendorinvoicerules.frm' (errno: 150).
I checked if there already exists a file gshnew/vendorinvoicerules.frm' on disk which may couse the problem but this wasnt the case.
I renamed the myisam vendorinvoicerules to vendorinvoicerules2 and converted it to inodb  no problem there.
I made a completly new and vendorinvoicerules with only one int column test and tried to convert it to ino db. No luck.
So im thinking maybe there is a foreign key constraint thats causing the problem. So i checked all foreign key constraints in a dump of the database but there wheren none pointing to vendorinvoicerules.
So i guess its a bug. So this is my report

How to repeat:
I dont know if you can repeat
you might try creating to inodb tables with a foreign key constraint on a varchar field and dropping one of them
[19 Feb 2005 12:58] Heikki Tuuri
Hi!

It means a foreign key error. Please check with

SHOW INNODB STATUS

a detailed description of the error.

Regards,

Heikki