Cascade types and behavior in Spring Boot - Step-by-Step Execution

Concept Flow - Cascade types and behavior

Start Operation on Parent Entity

↓

Check Cascade Type

↓

ALL

↓

Apply to Child Entities

↓

Execute DB Operation on Parent and Children

↓

End

When you perform an action on a parent entity, the cascade type decides if and how that action applies to its related child entities.

Execution Sample

Spring Boot

@Entity
class Parent {
  @OneToMany(cascade = CascadeType.PERSIST)
  List<Child> children;
}

parentRepository.save(parent);

Saving a parent entity with CascadeType.PERSIST also saves its new child entities automatically.

Execution Table

Step	Operation on Parent	Cascade Type	Action on Children	Database Operation
1	Call save(parent)	CascadeType.PERSIST	Persist new children	Insert parent and children rows
2	Call remove(parent)	CascadeType.PERSIST	No action on children	Delete parent row only
3	Call save(parent)	CascadeType.ALL	Persist new children	Insert parent and children rows
4	Call remove(parent)	CascadeType.ALL	Remove children	Delete children and parent rows
5	Call save(parent)	No cascade	No action on children	Insert parent row only
6	Call remove(parent)	No cascade	No action on children	Delete parent row only
7	End	-	-	-

💡 Operations stop after applying cascade rules and database actions.

Variable Tracker

Variable	Start	After Step 1	After Step 4	Final
parent	Detached	Managed (saved)	Managed (saved)	Managed
children	Detached	Managed (persisted if cascade)	Removed if cascade REMOVE	Depends on cascade

Key Moments - 2 Insights

Why don't children get deleted when CascadeType.PERSIST is used and parent is removed?

Because CascadeType.PERSIST only cascades save operations, not remove. See execution_table rows 2 and 4 for difference.

What happens if no cascade type is set and parent is saved?

Only the parent is saved; children remain detached and are not saved automatically. See execution_table row 5.

Visual Quiz - 3 Questions

Look at the execution table, what happens to children when parent is removed with CascadeType.ALL?

A Children are also removed from the database

B Children remain unchanged

C Children are saved again

D Operation fails with error

💡 Hint

Check execution_table row 4 for CascadeType.ALL remove operation

At which step do children get persisted automatically when saving parent?

A Step 2

B Step 1

C Step 5

D Step 6

💡 Hint

Look at execution_table rows where CascadeType.PERSIST is used on save

If cascade is removed, what changes in the database operations when saving parent?

A Children are saved automatically

B Both parent and children are deleted

C Only parent is saved, children are ignored

D Children are removed

💡 Hint

Refer to execution_table row 5 for no cascade save behavior

Concept Snapshot

Cascade Types in Spring Boot JPA:
- CascadeType.PERSIST: saves new children when parent saved
- CascadeType.REMOVE: deletes children when parent deleted
- CascadeType.ALL: applies all cascade operations
- No cascade: parent operations do not affect children
Use cascade to control related entity operations automatically.

Full Transcript

In Spring Boot JPA, cascade types control how operations on a parent entity affect its child entities. When you save or delete a parent, cascade settings decide if children are also saved or deleted. For example, CascadeType.PERSIST saves new children when the parent is saved but does not delete children when the parent is removed. CascadeType.ALL applies all operations including save and delete to children. Without cascade, operations on the parent do not affect children. This visual trace shows step-by-step how different cascade types behave during save and remove operations.