In some cases the constraints will propagate the delete, in other cases they won't. These differences are by design. There are good design reasons for no letting "delete biblio" table
Hi Robin, I'm aware about turning foreign keys constrains off is risky, what I was trying to know is how risky could be, but OK, I realize that depends of each database, and always a bad idea. So at least we can say manual (and also bulkmarkimport.pl -d option) should be updated (MySQL >~5.5)* adding a note about DELETE FROM biblio way not always will work right away. This bring us to: propagate in all/any cases? Propagation in any case will make really simple to update manual and bulkmarkimport. *I'll then fill a bug report about this two issues (manual and bulkmarkimport -d option) update. Regards, Pablo