How to parse the code of four ways for MyBatis Mapper to accept parameters
What this article shares to you is about how to parse the code of four ways of MyBatis Mapper accepting parameters, the editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article. Without saying much, let's take a look at it.
For a single parameter, you can write # {param} directly. There is no limit to the placeholder name here. Anyway, there is only one placeholder for one parameter, and there is no need to specify a name.
For multiple parameters, there are four common ways
Sort numbers by location
Public interface UserDao {public Integer addUser (String username, String password);}
Corresponding fragments in the mapper file
Insert into users (username, password) values (# {param1}, # {param2})
POJO object passed in
Public interface UserDao {public Integer addUser (String username, String password);}
Corresponding fragments in the mapper file
Insert into users (username, password) values (# {username}, # {password})
Map object passed in
# {} in public interface UserDao {/ / mapper accesses public Integer addUser (Map map) through key in map;}
Corresponding fragments in the mapper file
Insert into users (username, password) values (# {username}, # {password})
@ Param annotation (another form of Map object)
The value in the public interface UserDao {/ / annotation is map's key public Integer addUser (@ Param ("name") String username, @ Param ("word") String password);}
Corresponding fragments in the mapper file
Insert into users (username, password) values (# {name}, # {word})
The above is how to parse the code of four ways for MyBatis Mapper to accept parameters, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.
