Cascade types and behavior in Spring Boot

Introduction

Cascade types help manage related data automatically. They make sure changes in one object affect connected objects without extra code.

When saving a parent object and you want its child objects saved too.

When deleting a parent and you want all its related children deleted automatically.

When updating a parent and you want changes to reflect on its related children.

When detaching a parent from the database and you want to detach its children as well.

When refreshing a parent object and you want to refresh its related children.

Syntax

Spring Boot

@OneToMany(cascade = CascadeType.ALL)
private List<Child> children;

Use cascade attribute inside relationship annotations like @OneToMany, @ManyToOne, @OneToOne, or @ManyToMany.

CascadeType.ALL means all cascade operations apply: persist, merge, remove, refresh, detach.

Examples

This saves the orders automatically when the parent is saved.

Spring Boot

@OneToMany(cascade = CascadeType.PERSIST)
private List<Order> orders;

This updates and deletes the profile when the parent is updated or deleted.

Spring Boot

@OneToOne(cascade = {CascadeType.MERGE, CascadeType.REMOVE})
private Profile profile;

This detaches tags from the persistence context when the parent is detached.

Spring Boot

@ManyToMany(cascade = CascadeType.DETACH)
private Set<Tag> tags;

Sample Program

This example shows a Parent entity with children. When the parent is saved, all children are saved automatically because of CascadeType.ALL. The output shows how many children were saved and retrieved.

Spring Boot

import jakarta.persistence.*;
import java.util.*;

@Entity
class Parent {
    @Id
    @GeneratedValue
    private Long id;

    public Long getId() {
        return id;
    }

    @OneToMany(cascade = CascadeType.ALL, orphanRemoval = true)
    private List<Child> children = new ArrayList<>();

    public Parent() {}

    public void addChild(Child child) {
        children.add(child);
    }

    public List<Child> getChildren() {
        return children;
    }
}

@Entity
class Child {
    @Id
    @GeneratedValue
    private Long id;

    private String name;

    public Child() {}

    public Child(String name) {
        this.name = name;
    }

    public String getName() {
        return name;
    }
}

public class CascadeDemo {
    public static void main(String[] args) {
        EntityManagerFactory emf = Persistence.createEntityManagerFactory("example-unit");
        EntityManager em = emf.createEntityManager();

        em.getTransaction().begin();

        Parent parent = new Parent();
        parent.addChild(new Child("Child 1"));
        parent.addChild(new Child("Child 2"));

        em.persist(parent); // saves parent and children because of cascade

        em.getTransaction().commit();

        em.getTransaction().begin();
        Parent foundParent = em.find(Parent.class, parent.getId());
        System.out.println("Children count: " + foundParent.getChildren().size());
        em.getTransaction().commit();

        em.close();
        emf.close();
    }
}

Important Notes

Be careful with CascadeType.REMOVE to avoid accidentally deleting related data.

Use orphanRemoval = true to delete child objects if they are removed from the parent's collection.

Cascade only works on entity relationships managed by JPA, not on unrelated objects.

Summary

Cascade types automate saving, updating, deleting related entities.

Use cascade to keep related data consistent without extra code.

Choose cascade types carefully to avoid unwanted data loss.

Practice

1. What does the CascadeType.ALL option do in Spring Boot JPA?

easy

A. It applies all cascade operations including persist, merge, remove, refresh, and detach.

B. It only cascades the persist operation to related entities.

C. It disables all cascade operations.

D. It only cascades the remove operation to related entities.

Solution

1. Step 1: Understand CascadeType.ALL meaning

   CascadeType.ALL means all cascade operations are applied to related entities automatically.

2. Step 2: Identify included operations

   These operations include persist, merge, remove, refresh, and detach, covering all common entity lifecycle events.

3. Final Answer:

   It applies all cascade operations including persist, merge, remove, refresh, and detach. -> Option A

4. Quick Check:

   CascadeType.ALL = all cascade operations [OK]

Hint: ALL means every cascade action is applied automatically [OK]

Common Mistakes:

• Thinking ALL only means persist or remove
• Confusing cascade with fetch types
• Assuming cascade disables operations

2. Which of the following is the correct syntax to apply cascade persist on a JPA relationship in Spring Boot?

easy

A. @OneToMany(cascade = "persist")

B. @OneToMany(cascade = CascadeType.PERSIST)

C. @OneToMany(cascade = {"persist"})

D. @OneToMany(cascade = CascadeType.ALL.PERSIST)

Solution

1. Step 1: Recall correct cascade syntax

   The cascade attribute expects an array or single enum value of type CascadeType.

2. Step 2: Validate each option

   @OneToMany(cascade = CascadeType.PERSIST) uses correct enum CascadeType.PERSIST. String-based options like "persist" or {"persist"} are incorrect. CascadeType.ALL.PERSIST uses invalid enum chaining.

3. Final Answer:

   @OneToMany(cascade = CascadeType.PERSIST) -> Option B

4. Quick Check:

   Use CascadeType enums, not strings [OK]

Hint: Use CascadeType.PERSIST enum, not string quotes [OK]

Common Mistakes:

• Using string values instead of enum constants
• Trying to chain enums like ALL.PERSIST
• Omitting the cascade attribute entirely

3. Given the following code snippet, what happens when parentRepository.delete(parent) is called?

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

medium

A. An exception is thrown because cascade REMOVE is invalid here.

B. Only the parent entity is deleted; children remain in the database.

C. Both parent and all its children are deleted from the database.

D. Children are detached but not deleted; parent is deleted.

Solution

1. Step 1: Understand CascadeType.REMOVE effect

   CascadeType.REMOVE means deleting the parent also deletes all related children automatically.

2. Step 2: Apply to the delete operation

   Calling delete on parent triggers removal of parent and cascades delete to all children in the list.

3. Final Answer:

   Both parent and all its children are deleted from the database. -> Option C

4. Quick Check:

   REMOVE cascades delete to children [OK]

Hint: REMOVE cascades delete to related entities [OK]

Common Mistakes:

• Assuming children remain after parent delete
• Confusing REMOVE with DETACH or REFRESH
• Thinking cascade REMOVE causes errors

4. Identify the error in this code snippet related to cascade types:

@Entity
class Order {
  @OneToOne(cascade = CascadeType.MERGE)
  Payment payment;
}

// Later in code
orderRepository.save(order);

What issue might occur?

medium

A. The payment entity will not be saved if it is new, causing an error.

B. The cascade MERGE will cause duplicate payment entries.

C. The code will throw a syntax error due to cascade misuse.

D. The order entity will not be saved because cascade is missing.

Solution

1. Step 1: Understand CascadeType.MERGE behavior

   CascadeType.MERGE only updates existing entities; it does not persist new ones automatically.

2. Step 2: Analyze save operation with new payment

   If payment is new (not yet saved), save(order) won't persist payment, causing an error or missing data.

3. Final Answer:

   The payment entity will not be saved if it is new, causing an error. -> Option A

4. Quick Check:

   MERGE does not persist new entities [OK]

Hint: MERGE updates only; use PERSIST to save new entities [OK]

Common Mistakes:

• Assuming MERGE saves new entities
• Confusing syntax errors with runtime behavior
• Ignoring cascade effects on related entities

5. You have a Customer entity with a @OneToMany relationship to Order entities. You want to ensure that when a customer is deleted, all their orders are also deleted, but when an order is updated, the customer should not be affected. Which cascade type configuration is best?

hard

A. @OneToMany(cascade = CascadeType.DETACH)

B. @OneToMany(cascade = CascadeType.ALL)

C. @OneToMany(cascade = {CascadeType.PERSIST, CascadeType.MERGE})

D. @OneToMany(cascade = CascadeType.REMOVE)

Solution

1. Step 1: Identify cascade needed for delete

   To delete all orders when customer is deleted, CascadeType.REMOVE is required.

2. Step 2: Avoid affecting customer on order update

   Using only REMOVE avoids cascading updates or persists from orders to customer, so customer stays unchanged on order update.

3. Final Answer:

   @OneToMany(cascade = CascadeType.REMOVE) -> Option D

4. Quick Check:

   REMOVE cascades delete only, no update cascade [OK]

Hint: Use REMOVE to cascade deletes only, not updates [OK]

Common Mistakes:

• Using ALL cascades causing unwanted updates
• Using PERSIST or MERGE alone missing delete cascade
• Confusing DETACH with delete cascade