If I have an InnoDB DB with foreign key constraints, and the constraints on the tables are not in alphabetical order, an error will occur saying a table cannot be deleted in the old DB.
Fixed in subversion, thanks for reporting.
Please confirm using the patches taken from the scripts changed for QA_3_2 here
http://phpmyadmin.svn.sourceforge.net/viewvc/phpmyadmin?view=rev&revision=13203
I am now getting this error: Error: mySlidetablestatistics_indexes is undefined Source File: http://localhost/phpmyadmin/tbl_structure.php?db=mydb&table=mytable&token= Line: 619
Names changed in URL and token was left out, but I think you can see what I mean.
Nevermind, that's unrelated to the patch.
At least, does the patch fix your problem? You can also download version 3.2.5-rc1 that contains this fix.
Well, I no longer get the errors, but the foreign keys are gone which I think is a bug.
This is with the a patch from the files at that revision you gave me.
I'm testing 3.2.5-rc1 now
When the DB is renamed now, the Foreign Keys are gone.
It works in my testing, so please attach here an export of your db structure (at least a minimal structure to reproduce this problem).
Fixed in subversion, thanks for reporting.
Please confirm using the patches taken from the scripts changed for QA_3_2 here
http://phpmyadmin.svn.sourceforge.net/viewvc/phpmyadmin?view=rev&revision=13203
I am now getting this error:
Error: mySlidetablestatistics_indexes is undefined
Source File: http://localhost/phpmyadmin/tbl_structure.php?db=mydb&table=mytable&token=
Line: 619
Names changed in URL and token was left out, but I think you can see what I mean.
Nevermind, that's unrelated to the patch.
At least, does the patch fix your problem? You can also download version 3.2.5-rc1 that contains this fix.
Well, I no longer get the errors, but the foreign keys are gone which I think is a bug.
This is with the a patch from the files at that revision you gave me.
I'm testing 3.2.5-rc1 now
When the DB is renamed now, the Foreign Keys are gone.
It works in my testing, so please attach here an export of your db structure (at least a minimal structure to reproduce this problem).