JpaRepository interface in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the JpaRepository interface in Spring Data JPA?

The JpaRepository interface provides CRUD (Create, Read, Update, Delete) operations and pagination support for JPA entities, simplifying database access without writing boilerplate code.

intermediate

Which interface does JpaRepository extend to provide basic CRUD methods?

JpaRepository extends PagingAndSortingRepository, which itself extends CrudRepository. This means it inherits methods for CRUD and pagination.

intermediate

Name two useful methods provided by JpaRepository that are not in CrudRepository.

1. findAll(Pageable pageable) for pagination.
2. flush() to synchronize the persistence context to the database immediately.

beginner

How do you define a repository interface for an entity Book with an ID of type Long using JpaRepository?

You create an interface like this:

public interface BookRepository extends JpaRepository<Book, Long> {}

This gives you all CRUD and pagination methods for Book.

beginner

True or False: You need to write SQL queries manually when using JpaRepository for basic CRUD operations.

False. JpaRepository provides built-in methods for basic CRUD operations, so you don't need to write SQL manually for those.

What does JpaRepository primarily provide?

A Security features

B Only SQL query execution

C UI components for Spring Boot

D CRUD operations and pagination support

JpaRepository offers CRUD and pagination methods for JPA entities.

Which method is NOT part of JpaRepository?

A executeUpdate()

B findAll()

C save()

D deleteById()

executeUpdate() is not a method in JpaRepository. It is used in JPA Query API, not repository interfaces.

To add pagination support, which method would you use from JpaRepository?

A findAll(Pageable pageable)

B findById()

C saveAll()

D flush()

findAll(Pageable pageable) returns a page of entities, enabling pagination.

What type parameters does JpaRepository require?

A No type parameters

B Entity type only

C Entity type and ID type

D ID type only

JpaRepository needs the entity class and the type of its primary key.

Which interface is a direct parent of JpaRepository?

A CrudRepository

B PagingAndSortingRepository

C Repository

D EntityManager

JpaRepository extends PagingAndSortingRepository, which extends CrudRepository.

Explain how JpaRepository simplifies database operations in Spring Boot applications.

Think about what common database tasks you avoid writing manually.

Describe how to create a repository interface for an entity using JpaRepository and what benefits it brings.

Focus on the interface declaration and what you get from it.

Practice

1. What is the primary purpose of the JpaRepository interface in Spring Boot?

easy

A. To provide built-in methods for database operations on entities

B. To define the structure of REST API endpoints

C. To manage application security and authentication

D. To handle frontend UI rendering

Solution

1. Step 1: Understand JpaRepository role

   JpaRepository is designed to simplify database access by providing ready-made methods like save, findAll, and delete for entity classes.

2. Step 2: Compare with other options

   Options A, C, and D relate to REST API endpoints, security, and UI rendering, which are not responsibilities of JpaRepository.

3. Final Answer:

   To provide built-in methods for database operations on entities -> Option A

4. Quick Check:

   JpaRepository = database helper [OK]

Hint: JpaRepository = database methods for entities [OK]

Common Mistakes:

• Confusing JpaRepository with REST controllers
• Thinking it manages security
• Assuming it handles UI rendering

2. Which of the following is the correct way to declare a repository interface for an entity User with primary key type Long using JpaRepository?

easy

A. public interface UserRepository extends Repository<User> {}

B. public class UserRepository implements JpaRepository {}

C. public interface UserRepository extends JpaRepository {}

D. public interface UserRepository extends JpaRepository {}

Solution

1. Step 1: Check JpaRepository declaration syntax

   JpaRepository is an interface that should be extended, not implemented. The generic parameters are , so is correct.

2. Step 2: Validate each option

   public interface UserRepository extends JpaRepository {} correctly extends JpaRepository with . public class UserRepository implements JpaRepository {} incorrectly uses implements and class. public interface UserRepository extends JpaRepository {} swaps generic types. public interface UserRepository extends Repository<User> {} uses Repository, not JpaRepository.

3. Final Answer:

   public interface UserRepository extends JpaRepository {} -> Option D

4. Quick Check:

   Extend JpaRepository [OK]

Hint: Extend JpaRepository interface [OK]

Common Mistakes:

• Using implements instead of extends
• Swapping generic type order
• Using Repository instead of JpaRepository

3. Given the following repository method declaration:

List<User> findByLastName(String lastName);

What will this method do when called with findByLastName("Smith")?

medium

A. Return all User entities with lastName exactly 'Smith'

B. Return all User entities with lastName containing 'Smith'

C. Return a single User entity with lastName 'Smith'

D. Throw a runtime error because the method is invalid

Solution

1. Step 1: Understand method naming convention

   JpaRepository supports query derivation by method names. 'findByLastName' means find all entities where lastName equals the given parameter.

2. Step 2: Analyze return type and behavior

   The return type is List<User>, so it returns all matching users with lastName exactly 'Smith'. It does not do partial matching or throw errors.

3. Final Answer:

   Return all User entities with lastName exactly 'Smith' -> Option A

4. Quick Check:

   findByProperty = exact match [OK]

Hint: findByX = exact match, returns list if List type [OK]

Common Mistakes:

• Assuming it does partial matching
• Expecting a single result instead of list
• Thinking method is invalid without @Query

4. Consider this repository interface:

public interface ProductRepository extends JpaRepository {
    List<Product> findByPriceGreaterThan(Double price);
}

Which of the following is a likely cause of a runtime error when calling findByPriceGreaterThan(null)?

medium

A. JpaRepository does not support comparison keywords like GreaterThan

B. Method name is invalid and causes compile error

C. Passing null causes a NullPointerException in the query generation

D. The return type List<Product> is incorrect

Solution

1. Step 1: Check method name and support

   JpaRepository supports keywords like GreaterThan for query derivation, so method name is valid and compiles fine.

2. Step 2: Analyze passing null parameter

   Passing null to a comparison query causes a NullPointerException at runtime because the query cannot compare with null.

3. Final Answer:

   Passing null causes a NullPointerException in the query generation -> Option C

4. Quick Check:

   Null param in comparison query = runtime error [OK]

Hint: Never pass null to comparison query methods [OK]

Common Mistakes:

• Thinking method name is invalid
• Assuming JpaRepository lacks GreaterThan support
• Believing return type causes error

5. You want to add a custom method to your OrderRepository that finds all orders placed between two dates. Which of the following method signatures correctly uses JpaRepository naming conventions to achieve this?

hard

A. List<Order> findOrdersBetweenDates(LocalDate start, LocalDate end);

B. List<Order> findByOrderDateBetween(LocalDate start, LocalDate end);

C. List<Order> getOrdersByDateRange(LocalDate start, LocalDate end);

D. List<Order> findByOrderDateRange(LocalDate start, LocalDate end);

Solution

1. Step 1: Recall JpaRepository method naming rules

   JpaRepository supports keywords like Between to filter values between two parameters. The property name must match entity field, here 'OrderDate'.

2. Step 2: Evaluate each method signature

   List<Order> findByOrderDateBetween(LocalDate start, LocalDate end); uses 'findByOrderDateBetween' which is correct. Options B, C, and D use unsupported or incorrect keywords and will not work.

3. Final Answer:

   List<Order> findByOrderDateBetween(LocalDate start, LocalDate end); -> Option B

4. Quick Check:

   Use Between keyword for range queries [OK]

Hint: Use 'Between' keyword for range queries in method name [OK]

Common Mistakes:

• Using unsupported keywords like 'Range' or 'BetweenDates'
• Not matching property name exactly
• Trying to create custom method without @Query but wrong name