Why CRUD methods (save, findById, findAll, delete) in Spring Boot? - Purpose & Use Cases

The Big Idea

What if you could manage all your data with just a few simple commands instead of writing complex code every time?

The Scenario

Imagine building a web app where you must write separate code to add, find, list, and remove user data from a database every time.

You have to write SQL queries manually and handle database connections yourself.

The Problem

Writing all database operations manually is slow and error-prone.

It's easy to forget to close connections or write wrong queries, causing bugs and crashes.

Maintaining this code as your app grows becomes a nightmare.

The Solution

CRUD methods like save, findById, findAll, and delete in Spring Boot simplify database work.

They provide ready-made functions to add, find, list, and remove data safely and quickly.

This means less code, fewer bugs, and faster development.

Before vs After

✗ Before

Connection conn = DriverManager.getConnection(...);
Statement stmt = conn.createStatement();
stmt.executeUpdate("INSERT INTO users ...");
conn.close();

✓ After

userRepository.save(user);
User user = userRepository.findById(id).orElse(null);
List<User> users = userRepository.findAll();
userRepository.delete(user);

What It Enables

It enables developers to focus on app features instead of database details, making apps faster and more reliable.

Real Life Example

When you sign up on a website, the app uses save() to store your info, findById() to get your profile, findAll() to list users for admin, and delete() to remove accounts.

Key Takeaways

Manual database code is complex and error-prone.

CRUD methods provide simple, reusable database operations.

They speed up development and reduce bugs.

Practice

1. Which Spring Boot repository method is used to add a new entity or update an existing one in the database?

easy

A. save()

B. findById()

C. delete()

D. findAll()

Solution

1. Step 1: Understand the purpose of save()

   The save() method is designed to add a new entity or update an existing one in the database.

2. Step 2: Compare with other methods

   findById() and findAll() are for reading data, and delete() is for removing data, so they do not add or update.

3. Final Answer:

   save() -> Option A

4. Quick Check:

   Add or update data = save() [OK]

Hint: Remember: save = add or update data [OK]

Common Mistakes:

• Confusing save() with findById()
• Thinking delete() adds data
• Using findAll() to save data

2. Which of the following is the correct syntax to find an entity by its ID using Spring Boot's repository?

easy

A. repository.findById(id);

B. repository.save(id);

C. repository.delete(id);

D. repository.findAll(id);

Solution

1. Step 1: Identify the method to find by ID

   The method findById(id) is used to retrieve an entity by its ID.

2. Step 2: Check syntax correctness

   repository.findById(id); is the correct syntax. Other methods do not accept an ID to find an entity.

3. Final Answer:

   repository.findById(id); -> Option A

4. Quick Check:

   Find by ID syntax = repository.findById(id) [OK]

Hint: Use findById(id) to get one entity by its ID [OK]

Common Mistakes:

• Using save() to find an entity
• Passing ID to findAll(), which takes no parameters
• Using delete() to find data

3. Given the following code snippet, what will allUsers.size() return if the database has 3 user records?

List<User> allUsers = userRepository.findAll();
int count = allUsers.size();

medium

A. 0

B. 3

C. 1

D. null

Solution

1. Step 1: Understand findAll() behavior

   The findAll() method returns a list of all entities in the database.

2. Step 2: Count the number of records returned

   If the database has 3 user records, allUsers will contain 3 elements, so allUsers.size() returns 3.

3. Final Answer:

   3 -> Option B

4. Quick Check:

   findAll() returns all records count = 3 [OK]

Hint: findAll() returns all records as a list [OK]

Common Mistakes:

• Assuming findAll() returns null if no records
• Confusing size() with findById() result
• Thinking findAll() returns a single entity

4. What is wrong with this code snippet if it throws a compilation error?

userRepository.delete(5);

Assuming delete expects an entity object, not an ID.

medium

A. The ID must be a string, not an integer.

B. The method delete does not exist in Spring Boot repositories.

C. You must pass an entity object, not an ID, to delete.

D. You should use deleteById(5) instead to delete by ID.

Solution

1. Step 1: Understand delete method signature

   The delete method expects an entity object, not just an ID.

2. Step 2: Use correct method to delete by ID

   To delete by ID, use deleteById(id) method instead of delete(id).

3. Final Answer:

   You should use deleteById(5) instead to delete by ID. -> Option D

4. Quick Check:

   Delete by ID = deleteById(id) [OK]

Hint: Use deleteById(id) to remove by ID, not delete(entity) [OK]

Common Mistakes:

• Passing ID to delete() instead of entity
• Assuming delete() accepts ID directly
• Using wrong data type for ID

5. You want to update a user's email in the database using Spring Boot. Which sequence of repository methods correctly achieves this?

// Assume userId and newEmail are given
Optional<User> userOpt = userRepository.findById(userId);
if (userOpt.isPresent()) {
    User user = userOpt.get();
    user.setEmail(newEmail);
    // What next?
}

hard

A. Call userRepository.delete(user); then save(user);.

B. Call userRepository.findAll(); to refresh the list.

C. Call userRepository.save(user); to update the user.

D. No need to call any method; changes auto-save.

Solution

1. Step 1: Retrieve the user entity by ID

   The code uses findById(userId) to get the user object.

2. Step 2: Update the user and save changes

   After setting the new email, calling save(user) updates the database record.

3. Final Answer:

   Call userRepository.save(user); to update the user. -> Option C

4. Quick Check:

   Update data = findById + modify + save [OK]

Hint: Update entity fields then call save() to persist changes [OK]

Common Mistakes:

• Assuming changes auto-save without calling save()
• Deleting before saving to update
• Using findAll() to update a single record