Cascade types and behavior in Spring Boot - Mini Project: Build & Apply

Cascade Types and Behavior in Spring Boot

📖 Scenario: You are building a simple Spring Boot application to manage Authors and their Books. Each author can have multiple books. You want to understand how cascade types work so that when you save or delete an author, the related books are handled automatically.

🎯 Goal: Build two JPA entity classes Author and Book with a one-to-many relationship. Configure cascade types so that saving or deleting an author also saves or deletes their books.

📋 What You'll Learn

Create an Author entity with an id and name field

Create a Book entity with an id and title field

Set up a one-to-many relationship from Author to Book using @OneToMany

Add cascade type ALL to the relationship

Add orphanRemoval = true to remove books when they are no longer linked to an author

💡 Why This Matters

🌍 Real World

Managing related data entities like authors and books is common in library or publishing applications. Cascade types help keep data consistent automatically.

💼 Career

Understanding JPA cascade types is essential for backend developers working with Spring Boot and databases to manage entity relationships efficiently.

1

Create the Author entity

Create a Java class called Author annotated with @Entity. Add a private Long id field annotated with @Id and @GeneratedValue. Add a private String name field. Include public getters and setters for both fields.

Spring Boot

@Entity
public class Author {
    // Your code here
}

Hint

Remember to import javax.persistence.Entity, Id, and GeneratedValue annotations.

2

Create the Book entity

Create a Java class called Book annotated with @Entity. Add a private Long id field annotated with @Id and @GeneratedValue. Add a private String title field. Include public getters and setters for both fields.

Spring Boot

@Entity
public class Book {
    // Your code here
}

Hint

Make sure to add the same annotations as in Author for id and generate getters/setters.

3

Add one-to-many relationship with cascade

In the Author class, add a private List<Book> books field annotated with @OneToMany(cascade = CascadeType.ALL, orphanRemoval = true). Initialize it as an empty ArrayList<>(). Add public getter and setter for books.

Spring Boot

@Entity
public class Author {
    @Id
    @GeneratedValue
    private Long id;
    private String name;

    // Your code here

    public Long getId() {
        return id;
    }

    public void setId(Long id) {
        this.id = id;
    }

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }
}

Hint

Use java.util.List and java.util.ArrayList. Import javax.persistence.OneToMany and CascadeType.

4

Complete with bidirectional mapping (optional)

In the Book class, add a private Author author field annotated with @ManyToOne. Add public getter and setter for author. This completes the bidirectional relationship.

Spring Boot

@Entity
public class Book {
    @Id
    @GeneratedValue
    private Long id;
    private String title;

    // Add the author field with @ManyToOne annotation
    // Your code here
}

Hint

Import javax.persistence.ManyToOne and add getter/setter for author.

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