How to solve the problem that not all fields in mybatis update need to be updated

This article mainly introduces "how to solve the problem that not all fields of mybatis update need to be updated". In daily operation, I believe many people have doubts about how to solve the problem that not all fields of mybatis update need to be updated. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful for you to answer the doubt that "how to solve the problem that not all fields of mybatis update need to be updated." Next, please follow the editor to study!

Not all fields of mybatis update need to be updated

Mybatis update

Requirements: updated fields as parameters, unupdated fields are not passed in

Solutions update BS_USER ACCOUNT=# {ACCOUNT}, NAME=# {NAME}, PROV=# {PROV}, FAILURE_TIME=# {FAILURE_TIME}, where USERID=# {USERID}

Replace the set tag with

SuffixOverrides= "," in the tag means the last one to remove the comma.

Problems encountered in mybatis update

That's what xml says.

Update cw_base_resident_house_ref a set state = 0 where 1 and a.ID in # {item.refId}

After that, the error is reported, but the returned type is incorrect.

It turns out that the type in service and mapper is wrong. It is defined as list and should be defined as int.

At this point, the study on "how to solve the problem that not all fields of mybatis update need to be updated" is over. I hope to be able to solve everyone's doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!