Cascading delete
Cascading delete is the automatic propagation of a parent-record or resource deletion to associated dependent records or resources.
Java Persistence with Spring Data and Hibernate epub
Cascading deletion is the propagation of an entity removal operation to associated entities.
- How it is used
- Propagates removal from an aggregate-like Item entity to dependent Bid entities.
- How deep it goes
- Explains JPA lifecycle cascading, orphan removal, SQL efficiency, and database constraints, but does not detail transaction internals.
- Examples
- Uses Item–Bid mappings, repository deletion, orphan removal, and Hibernate @OnDelete configuration.
- What you can do after
- Configure and evaluate entity-level or database-level deletion propagation for associated entities.
Read how Java Persistence with Spring Data and Hibernate epub explains cascading delete →
.NET in Action, Second Edition
Cascade delete is a relational-data behavior in which deleting a principal record also deletes its related dependent records.
- How it is used
- Handles deletion of a principal record and its related dependents in an Entity Framework Core web API.
- How deep it goes
- Explains runtime failure and fixes it by eagerly loading dependent entities before deletion.
- Examples
- Uses a Book with related Ratings and an HTTP DELETE endpoint as the implementation example.
- What you can do after
- Diagnose and apply cascade deletion by loading related entities with Include before calling SaveChangesAsync.
Read how .NET in Action, Second Edition explains cascading delete →
Grokking Relational Database Design
CASCADE is a referential action that automatically propagates parent-row deletions or key updates to corresponding child rows.
- How it is used
- Uses referential actions to keep parent and child tables consistent during deletions.
- How deep it goes
- Defines automatic effects and shows foreign-key clauses, but does not detail execution internals.
- Examples
- Uses payment methods linked to users and company devices linked to employees to compare deletion outcomes.
- What you can do after
- Operate/configure it by adding ON DELETE CASCADE to a foreign-key constraint.
Read how Grokking Relational Database Design explains cascading delete →
Related concepts
- singleton sub-resourceuses · A singleton sub-resource is an API sub-resource representing one distinct related entity rather than a collection of entities.
- Entity Framework Coreused by · Entity Framework Core is a cross-platform object-relational mapping framework for .NET that enables applications to query and persist data through .NET objects and APIs.
- atomicityuses · Atomicity is the property that an operation or group of operations takes effect as an indivisible, all-or-nothing unit, without observable partial effects.
- ownershipuses · Ownership is a programming-language model that assigns responsibility for controlling a value or resource, including its lifetime and eventual cleanup.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.