Quick search:

cascaded delete

the automaitc deletion of dependent objects when an object is deleted

Dependent objects are objects that should not exist without the object they depend on. For example an object that represents the relation between two other objects in an n to m relationship should only exist if both related objects exist.

If the user wants to delete an object other objects depend on the application has two options:

  • delete the dependents too (maybe warn first)
  • refuse the delete as long as there are dependents. The user will have to delete the dependents first before he can delete the object(s) they depended on

The first option is 'cascaded delete'. The second we call delete protection. How to configure cascaded delete and delete protection.