I'm trying to find out how to make modules clean up after themselves when they're deleted, to avoid database bloat. So, when an editor deletes a module from a page, I want the module to remove all entries pertaining to itself from the relevant database tables.

Odd thing is, I haven't found any examples for this kind of thing anywhere. Am I not looking hard enough, or is there a reason why data from deleted modules needs to be kept? Can anybody point me in the right direction?

Ok, that's what I originally thought (I'm not an SQL expert). As per your suggestion, I've had a look at the core modules to see if the syntax created by the module framework builder was screwy. However, during testing I noticed that the core modules seem to have exactly the same problem. As far as I can see, all core modules have a variation of the following in their SqlDataProvider file:

ALTER TABLE {databaseOwner}[{objectQualifier}HtmlText] WITH NOCHECK ADD CONSTRAINT [FK_{objectQualifier}HtmlText_{objectQualifier}Modules] FOREIGN KEY ([ModuleID]) REFERENCES {databaseOwner}[{objectQualifier}Modules] ([ModuleID]) ON DELETE CASCADE NOT FOR REPLICATION

Ah, yes, that's solved the mystery!

Thanks a million to both of you!

Frauke