Setsql function and risk of using lamdbaupdatewrapper

---

title: Use LamdbaUpdateWrapper Of setSql Role and risk
date: 2022-04-12 18:10:34
tags: java

---

Problem introduction

Think about it first ： We need to update a piece of data in the database , And want to modify a field based on the original , What shall we do ？

Under normal circumstances , We need to find out before updating , But I just want to update it directly , Then you need to Mapper Write in sql, It's hard for a field , Use in this case LamdbaUpdateWrapper Of setSql() The method can .

// hold num Field plus 5LambdaUpdateWrapper<User> updateWrapper = Wrappers.<User>lambdaUpdate()	.eq(User::getId, userId)	.setSql("count = count + 5");userService.update(updateWrapper);

BUT, In this way, there may be risks , Mainly for testing mybatis-plus, Whether to take preventive measures , After testing , did not .

For example, use the most common sleep(), Add this part to sql In the paragraph + sleep(5)

LambdaUpdateWrapper<User> updateWrapper = Wrappers.<User>lambdaUpdate()                .eq(User::getId, userId)                .setSql("count = count + 5 + sleep(5)");

But then again , This is what developers can access , Just to prove mybatis-plus It did not setSql() To filter , It's a direct way to spell it up .

Daily words

The above is the use of LamdbaUpdateWrapper Of setSql Full contents of functions and risks

Copyright notice ：
Original Blogger ： Cowherd Conan
Personal blog links ：https://www.keafmd.top/

If it helps you , Thank you for clicking on == One key, three links == Support ！
[ ha-ha ][ Huai Quan ]

come on. ！

Joint efforts ！

Keafmd

You can see it here , You know the following , Let's make progress together ！