@OneToMany relationship in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the @OneToMany annotation represent in Spring Boot?

It represents a relationship where one entity is linked to many instances of another entity, like one author having many books.

intermediate

In a @OneToMany relationship, which side owns the relationship by default?

The "many" side owns the relationship by default, meaning it holds the foreign key in the database.

intermediate

How do you specify the field that owns the relationship in a @OneToMany mapping?

You use the 'mappedBy' attribute on the @OneToMany annotation to point to the owning field on the 'many' side.

intermediate

What is the effect of using CascadeType.ALL in a @OneToMany relationship?

It means that operations like save, update, or delete on the parent entity will automatically apply to the related child entities.

beginner

Why is it important to use a collection type like List or Set in a @OneToMany relationship?

Because one entity relates to many others, a collection holds all related entities, allowing easy access and management.

What annotation is used on the 'one' side to define a one-to-many relationship?

A @OneToMany

B @ManyToOne

C @ManyToMany

D @OneToOne

The @OneToMany annotation defines the 'one' side of a one-to-many relationship.

Which attribute tells JPA which field owns the relationship in @OneToMany?

A cascade

B targetEntity

C mappedBy

D fetch

The 'mappedBy' attribute points to the owning field on the 'many' side.

If you want changes in the parent entity to affect child entities automatically, which CascadeType should you use?

A CascadeType.ALL

B CascadeType.MERGE

C CascadeType.NONE

D CascadeType.DETACH

CascadeType.ALL applies all operations like save, update, and delete to child entities.

In a @OneToMany relationship, where is the foreign key stored?

A In the 'one' side table

B No foreign key is used

C In a join table

D In the 'many' side table

The foreign key is stored in the 'many' side table pointing back to the 'one' side.

Which Java collection is commonly used to hold related entities in a @OneToMany relationship?

A Map

B List

C Queue

D Stack

List or Set are commonly used to hold multiple related entities.

Explain how the @OneToMany annotation works in Spring Boot and how it connects two entities.

Think about how one author can have many books and how the database knows this.

Describe the role of cascade types in a @OneToMany relationship and why they are useful.

Imagine deleting an author and wanting all their books deleted automatically.

Practice

1. What does the @OneToMany annotation represent in Spring Boot JPA?

easy

A. A relationship where one entity is linked to many entities

B. A relationship where many entities are linked to one entity

C. A way to delete entities automatically

D. A method to fetch data lazily

Solution

1. Step 1: Understand the meaning of @OneToMany

   The annotation defines a connection where one object relates to multiple objects, like one author having many books.

2. Step 2: Differentiate from other relationships

   @ManyToOne is the opposite, linking many entities to one. @OneToMany specifically means one to many.

3. Final Answer:

   A relationship where one entity is linked to many entities -> Option A

4. Quick Check:

   @OneToMany = one to many link [OK]

Hint: Think 'one' object owns 'many' related objects [OK]

Common Mistakes:

• Confusing @OneToMany with @ManyToOne
• Thinking it deletes entities automatically
• Assuming it controls fetch type only

2. Which of the following is the correct way to declare a @OneToMany relationship in an entity class?

easy

A. @OneToMany(mappedBy = "parent") private List<Child> children;

B. @OneToMany private Child child;

C. @OneToMany(mappedBy = "children") private Child parent;

D. @OneToMany private Map childrenMap;

Solution

1. Step 1: Check the collection type for @OneToMany

   @OneToMany requires a collection like List or Set to hold multiple related entities, so List<Child> is correct.

2. Step 2: Verify the mappedBy attribute usage

   mappedBy should point to the field name in the Child entity that owns the relationship, here "parent" is correct.

3. Final Answer:

   @OneToMany(mappedBy = "parent") private List<Child> children; -> Option A

4. Quick Check:

   Use collection + mappedBy for correct syntax [OK]

Hint: Use a collection and mappedBy to link entities [OK]

Common Mistakes:

• Using single object instead of collection
• Wrong mappedBy value
• Using Map instead of List or Set

3. Given the following code snippet, what will be the output when fetching a Department entity?

@Entity
public class Department {
  @Id
  private Long id;

  @OneToMany(mappedBy = "department", fetch = FetchType.EAGER)
  private List<Employee> employees;

  // getters and setters
}

Assuming the department has 3 employees, what happens when you load the department?

medium

A. Only one employee is loaded due to default limit

B. The department loads without employees until accessed

C. The department loads with all 3 employees immediately

D. An error occurs because fetch type is invalid

Solution

1. Step 1: Understand fetch type EAGER

   FetchType.EAGER means related entities are loaded immediately with the main entity.

2. Step 2: Apply to the employees list

   Since employees are marked EAGER, all 3 employees will be loaded when the department is fetched.

3. Final Answer:

   The department loads with all 3 employees immediately -> Option C

4. Quick Check:

   FetchType.EAGER loads related entities immediately [OK]

Hint: EAGER fetch loads all related data immediately [OK]

Common Mistakes:

• Confusing EAGER with LAZY fetch
• Assuming default fetch loads lazily
• Expecting errors from fetch type

4. Identify the error in this @OneToMany mapping:

@Entity
public class Order {
  @Id
  private Long id;

  @OneToMany
  private List<Item> items;

  // getters and setters
}

Why might this cause issues when saving an Order with Items?

medium

A. List<Item> should be Set<Item> for @OneToMany

B. Missing mappedBy causes owning side confusion

C. The @Id annotation is missing

D. Items should be annotated with @ManyToMany

Solution

1. Step 1: Check ownership in bidirectional @OneToMany

   Without mappedBy, JPA doesn't know which side owns the relationship, causing extra join tables or errors.

2. Step 2: Understand impact on saving

   Without ownership, saving Order and Items may not link properly, causing data inconsistency.

3. Final Answer:

   Missing mappedBy causes owning side confusion -> Option B

4. Quick Check:

   mappedBy defines owner, missing it causes issues [OK]

Hint: Always set mappedBy on non-owning side [OK]

Common Mistakes:

• Omitting mappedBy in bidirectional relationships
• Confusing collection types for @OneToMany
• Misusing @ManyToMany instead of @OneToMany

5. You want to delete a Category and all its related Product entities automatically. Which @OneToMany configuration achieves this behavior?

hard

A. @OneToMany(cascade = CascadeType.PERSIST) private List<Product> products;

B. @OneToMany(mappedBy = "category") private List<Product> products;

C. @OneToMany(fetch = FetchType.LAZY) private List<Product> products;

D. @OneToMany(mappedBy = "category", cascade = CascadeType.ALL, orphanRemoval = true) private List<Product> products;

Solution

1. Step 1: Understand cascade and orphanRemoval

   CascadeType.ALL applies all operations including delete to related entities. orphanRemoval=true removes child entities if removed from parent.

2. Step 2: Apply to deleting Category

   With cascade ALL and orphanRemoval, deleting Category deletes all linked Products automatically.

3. Final Answer:

   @OneToMany(mappedBy = "category", cascade = CascadeType.ALL, orphanRemoval = true) private List<Product> products; -> Option D

4. Quick Check:

   Use cascade ALL + orphanRemoval for auto-delete [OK]

Hint: Cascade ALL + orphanRemoval deletes children automatically [OK]

Common Mistakes:

• Forgetting cascade causes children to remain
• Using only cascade PERSIST won't delete children
• Ignoring orphanRemoval for child removal