Deleting data
How an object is deleted, what happens to dependent objects and files, and what is left afterwards.
Topics in this subject area
- 1.How a DELETE runs
Check visibility, load, check roles, cascade, hooks, remove: the steps of a delete and the errors at each point. There is only hard deletion.
- 2.Dependent objects (cascades)
When children are deleted along with the parent and when they are only unlinked, that every child needs its own delete role, and that a missing role rolls back everything.
- 3.Deleting by changing
A PUT or PATCH that removes a dependent child from a list or a reference deletes it. This page explains when that happens.
- 4.Deleting file models
When a file model is deleted, the record, the file content and all retained versions disappear. The history of the record remains, the content does not.
- 5.What remains after a delete
The history stays readable, there is no recycle bin (soft delete), and a rollback does not bring deleted objects back.