<select id="getUserRolePage" parameterType="com.lazy.develop.model.UserRolQuery"
resultType="com.lazy.develop.model.UserRolePage">
SELECT
u.id,
u.login_name AS loginName,
u.`password`,
u.create_time AS createTime,
r.role_name AS roleName
FROM
`user` u
JOIN role r ON u.`level` = r.id
<where>
<if test="startTime != null">
u.create_time >= #{startTime,jdbcType=TIMESTAMP}
</if>
<if test="endTime != null">
AND u.create_time <= #{endTime,jdbcType=TIMESTAMP}
</if>
<if test="level != null">
AND u.level > #{level,jdbcType=BIGINT}
</if>
</where>
</select>
这种情况多数,我们需要2个model(UserRolQuery和UserRolePage)
<select id="getUserRolePage" parameterType="com.lazy.develop.model.Record"
resultType="com.lazy.develop.model.Record">
SELECT
u.id,
u.login_name AS loginName,
u.`password`,
u.create_time AS createTime,
r.role_name AS roleName
FROM
`user` u
JOIN role r ON u.`level` = r.id
<where>
<if test="startTime !='' and startTime != null">
u.create_time >= #{startTime,jdbcType=TIMESTAMP}
</if>
<if test="endTime !='' and endTime != null">
AND u.create_time <= #{endTime,jdbcType=TIMESTAMP}
</if>
<if test="level !='' and level != null">
AND u.level > #{level,jdbcType=BIGINT}
</if>
</where>
</select>
parameterType与resultType都是Record.class,但是因为是map,在取的时候都是字符串取值的,所以加空字符串判断。
@RequestMapping(value="/getById", method = RequestMethod.GET)
public Object getUserRolePage(@ModelAttribute UserRolQuery userRolQuery){
List<UserRolePage> user = userServiceImpl.getUserRolePage(userRolQuery);
return user;
}
①一旦参数发生变化,UserRolQuery就的发生修改
②一旦返回结果变化,UserRolePage也得发生修改
③以上2中情况发生,Mapper配置文件都得改
@RequestMapping(value="/getUserRolePage", method = RequestMethod.GET)
public Object getUserRolePage(HttpServletRequest request){
Record Record=new Record(request);
List<Record> user = userServiceImpl.getUserRolePage(Record);
return user;
}
4中①和②的情况,都只需要执行步骤③
给参数赋值什么的都不影响哈
@RequestMapping(value="/getUserRolePage", method = RequestMethod.GET)
public Object getUserRolePage(HttpServletRequest request){
Record record=new Record(request);
//record.put("name", "name"); //和普通的map使用一样
//String name=record.getString("name");
//Integer id=record.getInteger("id");
//Long id2=record.getLong("id");
//Object obj=record.get("user"); //目前就写了这几个,大家可以根据自己的需求改哈
List<Record> user = userServiceImpl.getUserRolePage(record);
return user;
}
这种开发模式,因为没的bean,所以要求注释就比较严谨,不然过段时间,自己都不知道里面有啥了,不过对与有bean的来说,内容多的话,你也不知道那个字段在用,那个没用了吧,总体来说,优缺点都很明显。
Record.class源码:https://cloud.tencent.com/developer/article/1147227