foreign key constraint fails errors

Hi
I, like many others have encountered this error when using PGC, this plugin is a great concept, but the, foreign key constraint issue needs to be looked at. For all but the simplest of Db’s this plugin will fail every time since foreign key relationships are a part of most well designed Dbs. I had about 40 redundant/deleted subsites in my MultiSite. On the plus side you can use the plugin to give you an insight to the garbage to be deleted then do the deletions manually, i used phpMyAdmin (and Adminer as its faster); phpMyAdmin does ask you before ‘dropping tables whether you want to disable foreign key checks; Adminer doesn’t – whichever GUI you use both will bulk delete without issue.

I think the plugin is excellent in terms of gathering the required tables for deletion. May i suggest that instead of offering to delete from the plugin itself that you dynamically create the SQL code which can be cut ‘n pasted into the users MYSQL client GUI of choice and do it from there were the foreign-key constraints can be better dealt with so long as you have sufficient MySQL privileges of course.

Just a suggestion otherwise a superb solution to an age-old WP problem. Of course the real solution would be to implement changes in the way 3rd-pary developers write plugins and ensure every plugin MUST implement FULL garbage collection on deletion of the plugin. Give the user the choice to preserve setting of ‘said’ plugin should they re-install it. However thats a WordPress Core issue.

Nice plugin, good work.