JPA执行Update操作后如何判断是否更新成功（至少有一条数据被更新）

Absolutely, you can totally pull this off without pre-checking if the email exists first! Here's a straightforward, efficient approach tailored to your code:

Step 1: Adjust the Repository Method to Return Updated Row Count #

Your current repository method returns void, which gives you no visibility into whether the update actually touched any records. By changing it to return an int, you’ll get the exact number of rows modified by the query—this is the key to solving your problem.

Update your repository code like this:

@Modifying
@Query("update User u set u.resetKey=:resetKey, u.enabled=false where u.username=:email")
int userForgetPassword(@Param("email") String email, @Param("resetKey") String resetPasswordKey);

(Quick note: I aligned the parameter name resetPasswordKey with the query's :resetKey placeholder to avoid mismatches—double-check these stay consistent!)

This return value will be 1 if a user with the provided email exists (and was successfully updated), and 0 if no matching user was found.

Step 2: Update the Service Logic to Use the Row Count #

Now in your service layer, you can use this returned count to decide whether to send the email. Only trigger the mail service if the update affected at least one row.

Modify your service method:

public void userForgetPassword(String email) {
    String resetPasswordKey = ...; // Keep your existing logic to generate the reset key
    int updatedRows = userRepository.userForgetPassword(email, resetPasswordKey);
    
    // Only send the email if the update actually succeeded (at least one record changed)
    if (updatedRows > 0) {
        mailService.sendHtmlMail(email);
    }
}

Why This Works #

• You skip an extra database call to validate the email’s existence—this is more efficient, since the update query inherently checks for the user’s presence.
• The row count gives you a direct, reliable signal of whether the update was successful, so no pre-validation steps are needed.

A quick configuration check: Most default JPA/Hibernate setups return the correct updated row count automatically, but if you run into issues, add this property to your application.properties or application.yml:

spring.jpa.properties.hibernate.query.return_native_query_updated_row_count=true

内容的提问来源于stack exchange，提问作者robert trudel