Shulou(Shulou.com)06/01 Report--

This article mainly introduces the relevant knowledge of "how EntityWrapper nests or statements in and conditions". The editor shows you the operation process through an actual case. The method of operation is simple and fast, and it is practical. I hope this article "how EntityWrapper nests or statements in and conditions" can help you solve the problem.

Nesting or statements in and conditions

Want to write a statement similar to the following:

Select * from table_1 where (coulmn_1 like'% XX%' or coulmn_1 like'% XX%') and del_flag='0'

But in the actual execution, mybatisplus parses it as:

Select * from table_1 where coulmn_1 like'% XX%' or coulmn_1 like'% XX%' and del_flag='0'

Obviously, since there are no parentheses, the conditions are different. Use andNew instead of and:

Wrapper.andNew ("del_flag='0'")

The final statement printed in the log is:

Select * from table_1 where (coulmn_1 like'% XX%' or coulmn_1 like'% XX%') and (del_flag='0')

The function of andNew is to act as another and ()!

Some interfaces of EntityWrapper explain that setSqlSelect sets SELECT query field whereWHERE statement, splicing-WHERE conditional andAND statement, splicing-AND field = value andNewAND statement, splicing-AND (field = value) orOR statement, splicing-OR field = value orNewOR statement, splicing-OR (field = value) eq equals = allEq based on map content = ne is not equal to gt greater than > ge greater than or equal to lt less than

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.