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

Recall & Review

beginner

What does the @ManyToOne annotation represent in Spring Boot JPA?

It represents a many-to-one relationship between two entities, where many instances of one entity relate to one instance of another entity.

beginner

In a @ManyToOne relationship, which side owns the foreign key in the database?

The entity with the @ManyToOne annotation owns the foreign key column in the database table.

intermediate

How do you specify the foreign key column name in a @ManyToOne relationship?

You use the @JoinColumn annotation with the name attribute to specify the foreign key column name.

intermediate

Can a @ManyToOne relationship be optional? How do you control this?

Yes, it can be optional. You control this by setting the optional attribute in @ManyToOne to true or false.

intermediate

What is the default fetch type for @ManyToOne and why is it important?

The default fetch type is EAGER, meaning the related entity is loaded immediately with the owner entity. This affects performance and loading behavior.

In a @ManyToOne relationship, which entity contains the foreign key column?

A Neither entity contains the foreign key

B The entity with the @ManyToOne annotation

C Both entities share the foreign key

D The entity with the @OneToMany annotation

The entity annotated with @ManyToOne owns the foreign key column in the database.

Which annotation is used to specify the foreign key column name in a @ManyToOne relationship?

A @JoinColumn

B @Column

C @ForeignKey

D @PrimaryKeyJoinColumn

@JoinColumn is used to define the foreign key column name in the owning entity.

What is the default fetch type of a @ManyToOne relationship in Spring Boot JPA?

A NONE

B LAZY

C DEFAULT

D EAGER

The default fetch type for @ManyToOne is EAGER, which loads the related entity immediately.

How do you make a @ManyToOne relationship optional?

A Set optional=true

B Use @Nullable annotation

C Set optional=false

D Use @NotNull annotation

Setting optional=true allows the relationship to be null, making it optional.

If you want to avoid loading the related entity immediately in a @ManyToOne relationship, what should you do?

A Set fetch=FetchType.EAGER

B Remove the @ManyToOne annotation

C Set fetch=FetchType.LAZY

D Use @Transient annotation

Setting fetch=FetchType.LAZY delays loading the related entity until it is accessed.

Explain how the @ManyToOne annotation works in Spring Boot JPA and how it relates to database foreign keys.

Think about how two tables connect with one foreign key column.

Describe how to control the optionality and fetch behavior of a @ManyToOne relationship.

Consider attributes inside the @ManyToOne annotation.

Practice

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

easy

A. A many-to-one relationship where many entities link to one entity

B. A one-to-many relationship where one entity links to many entities

C. A one-to-one relationship between two entities

D. A many-to-many relationship between two entities

Solution

1. Step 1: Understand relationship types in JPA

   @ManyToOne means many instances of an entity relate to one instance of another entity.

2. Step 2: Match the description to the annotation

   The annotation @ManyToOne specifically defines many entities pointing to one entity.

3. Final Answer:

   A many-to-one relationship where many entities link to one entity -> Option A

4. Quick Check:

   @ManyToOne = many entities to one entity [OK]

Hint: Remember: Many objects point to one with @ManyToOne [OK]

Common Mistakes:

• Confusing @ManyToOne with @OneToMany
• Thinking it means one-to-one
• Mixing it up with many-to-many

2. Which of the following is the correct way to declare a @ManyToOne relationship with a join column named category_id?

easy

A. @ManyToOne
@JoinColumn(name = "category_id")
private Category category;

B. @OneToMany
@JoinColumn(name = "category_id")
private Category category;

C. @ManyToOne
@JoinColumn(columnName = "category_id")
private Category category;

D. @ManyToOne
@JoinColumn(name = category_id)
private Category category;

Solution

1. Step 1: Check correct annotation usage

   The relationship is many-to-one, so @ManyToOne is correct.

2. Step 2: Verify @JoinColumn syntax

   The attribute to specify column name is name and the value must be a string in quotes.

3. Final Answer:

   @ManyToOne @JoinColumn(name = "category_id") private Category category; -> Option A

4. Quick Check:

   @JoinColumn uses name="column_name" [OK]

Hint: Use @JoinColumn(name = "column_name") with quotes [OK]

Common Mistakes:

• Using @OneToMany instead of @ManyToOne
• Using columnName instead of name in @JoinColumn
• Omitting quotes around column name

3. Given the entities below, what will be the output of System.out.println(order.getCustomer().getName()); if the order is linked to a customer named "Alice"?

public class Order {
  @ManyToOne
  @JoinColumn(name = "customer_id")
  private Customer customer;

  public Customer getCustomer() { return customer; }
}

public class Customer {
  private String name;
  public String getName() { return name; }
}

medium

A. Compilation error

B. customer_id

C. null

D. Alice

Solution

1. Step 1: Understand the relationship and method calls

   The order has a customer linked via @ManyToOne, so calling getCustomer() returns the Customer object.

2. Step 2: Access the customer's name

   Calling getName() on the Customer returns the customer's name, which is "Alice".

3. Final Answer:

   Alice -> Option D

4. Quick Check:

   order.getCustomer().getName() = "Alice" [OK]

Hint: Follow the chain: order -> customer -> name [OK]

Common Mistakes:

• Expecting the join column name instead of customer name
• Assuming null if not initialized
• Thinking it causes a compile error

4. Identify the error in the following code snippet that uses @ManyToOne:

@Entity
public class Book {
  @Id
  private Long id;
  @ManyToOne
  @JoinColumn(name = "author_id")
  private Author author;

  public Author getAuthor() { return author; }
  public void setAuthor(Author author) { this.author = author; }
}

@Entity
public class Author {
  private String name;
  public String getName() { return name; }
}

medium

A. Author class is missing @Entity annotation

B. Book class should use @OneToMany instead of @ManyToOne

C. Missing @Id annotation in Author class

D. Join column name should be "authorId" not "author_id"

Solution

1. Step 1: Check entity requirements

   Every JPA entity must have a primary key annotated with @Id. The Author class lacks this.

2. Step 2: Verify other annotations

   Author has @Entity but no @Id, which will cause runtime errors.

3. Final Answer:

   Missing @Id annotation in Author class -> Option C

4. Quick Check:

   Entity requires @Id field [OK]

Hint: Always add @Id to every entity class [OK]

Common Mistakes:

• Confusing relationship annotations
• Ignoring missing primary key
• Assuming join column naming causes error

5. You have two entities: Order and Customer. Each order belongs to one customer, but a customer can have many orders. You want to fetch all orders with their customers efficiently. Which approach correctly uses @ManyToOne for eager loading?

hard

A. Use @ManyToOne(fetch = FetchType.LAZY) on Order's customer and fetch customers separately

B. Use @ManyToOne(fetch = FetchType.EAGER) on Order's customer to load customers with orders

C. Use @OneToMany(fetch = FetchType.EAGER) on Customer's orders and no mapping on Order

D. Use @ManyToOne without fetch type and manually query customers for each order

Solution

1. Step 1: Understand fetch types in @ManyToOne

   By default, @ManyToOne uses FetchType.EAGER, loading the related customer eagerly with the order.

2. Step 2: Match the best approach

   Explicitly using fetch = FetchType.EAGER on the Order's customer field ensures efficient eager loading for this many-to-one relationship.

3. Final Answer:

   Use @ManyToOne(fetch = FetchType.EAGER) on Order's customer to load customers with orders -> Option B

4. Quick Check:

   @ManyToOne = EAGER by default [OK]

Hint: EAGER fetch on @ManyToOne loads related data together [OK]

Common Mistakes:

• Using LAZY fetch without proper query optimization
• Using @OneToMany on Customer without Order mapping
• Manually querying related entities inefficiently