MySQL giant pit: update updates should be judged with caution by affecting the number of rows!!!

source ：cnblogs.com/yjmyzz/p/13562182.html

In the business system , Use update Statement updating data is a normal scenario , We often pass through update Number of rows updated , To make some business judgments , Similar to the following pseudo code ：(mybatis + mysql scene )

if (xxxMapper.updateByPrimaryKeySelective(entity)>0){
   // The update is successful , Do other business processing 
}

But there's a hole ,mysql in update Number of rows affected >0 It's conditional , If there is a table ：

There's only one record in it （ID=1）, We use it update Update one ID=1 This record of

This line was successfully updated , The number of affected lines is 1, Taken for granted , Then put this update Statement again ：

Now , The number of affected rows returned is 0, in other words , When the record to be updated is the same as the old value of the original record ,mysql In fact, there will be no update ..

In other words , If the data transmitted from the upstream , Equal to the old value of the database itself , When there is no change ,update The number of lines affected by the statement is 0. This is different from another scenario ：" Update a record that doesn't exist , Affect the number of rows and return 0" Indistinguishable .

Conclusion ： Do not use update The number of lines affected by the statement makes important business judgments !

Recent hot article recommends ：

1.1,000+ Avenue Java Arrangement of interview questions and answers (2022 The latest version )

2. Explode ！Java Xie Cheng is coming ...

3.Spring Boot 2.x course , It's too complete ！

4. Don't write about the explosion on the screen , Try decorator mode , This is the elegant way ！！

5.《Java Development Manual （ Song Mountain version ）》 The latest release , Download it quickly ！

I think it's good , Don't forget to like it + Forward ！