JPA 多表嵌套+nativeQuery + Page分页

先看需求

微信截图_20190613234830.png

 

一共5个区域,分别对应5张表,作者表、文章列表、点赞记录表、评论表、阅读记录表

sql

写的有点水,有点渣。这里查询两次点赞记录表,要查看当前登录人是否点过赞

 SELECT  ar.id, ar.author, su.avatar,ar.user_id as userId, ar.title, ar.image_url as imageUrl, ar.create_date as createDate, ar.lastmodified_time as lastmodifiedTime,
		 ar.tag, ar.tag_id as tagId,ar.des,ar.status, arr.readTimes,alr.likeRecordTimes,alra.checklike,aco.commentTimes FROM article ar
	 LEFT JOIN (SELECT a.id,COUNT(rr.article) as readTimes FROM article a LEFT JOIN read_record rr ON rr.article = a.id GROUP BY a.id)  arr ON arr.id = ar.id
	LEFT JOIN (SELECT a.id,COUNT(lr.article) as likeRecordTimes FROM article a LEFT JOIN like_record lr ON lr.article = a.id GROUP BY a.id  ) alr ON alr.id = ar.id
	LEFT JOIN (SELECT a.id,lr.username as checklike FROM article a LEFT JOIN like_record lr ON lr.article = a.id and lr.username ='admin' ) alra ON alra.id = ar.id
	LEFT JOIN ( SELECT a.id,COUNT(co.article) as commentTimes FROM article a  LEFT JOIN comment co ON co.article = a.id GROUP BY a.id ) aco ON aco.id = ar.id 
	LEFT JOIN  sys_user su ON su.id = ar.user_id 
复制代码

jpa 实现

    @Query(value = " SELECT  ar.id, ar.author, su.avatar,ar.user_id as userId, ar.title, ar.image_url as imageUrl, ar.create_date as createDate, ar.lastmodified_time as lastmodifiedTime, " +
            "  ar.tag, ar.tag_id as tagId,ar.des,ar.status, arr.readTimes,alr.likeRecordTimes,alra.checklike,aco.commentTimes FROM article ar " +
            " LEFT JOIN (SELECT a.id,COUNT(rr.article) as readTimes FROM article a LEFT JOIN read_record rr ON rr.article = a.id GROUP BY a.id)  arr ON arr.id = ar.id " +
            " LEFT JOIN (SELECT a.id,COUNT(lr.article) as likeRecordTimes FROM article a LEFT JOIN like_record lr ON lr.article = a.id GROUP BY a.id  ) alr ON alr.id = ar.id  " +
            " LEFT JOIN (SELECT a.id,lr.username as checklike FROM article a LEFT JOIN like_record lr ON lr.article = a.id and lr.username =:username ) alra ON alra.id = ar.id " +
            " LEFT JOIN ( SELECT a.id,COUNT(co.article) as commentTimes FROM article a  LEFT JOIN comment co ON co.article = a.id GROUP BY a.id ) aco ON aco.id = ar.id " +
            " LEFT JOIN  sys_user su ON su.id = ar.user_id WHERE ar.status =:status and ar.tag_id =:tagId ",
            countQuery = "SELECT count(*) FROM article",
            nativeQuery = true)
    Page<Map<String, Object>> findByStatusAllAndTagId(@Param("username") String username, @Param("status") int status, @Param("tagId") int tagId, Pageable pageable);
复制代码

调用, 这里使用多字段排序

Sort sort = new Sort(Sort.Direction.DESC, "readTimes").and(new Sort(Sort.Direction.DESC, "create_date"));
PageRequest pageable = PageRequest.of(pageNo, pageSize, sort);
articleDao.findByStatusAllAndTagId(username, status, tagId, pageable);
复制代码
  • 这里的关键点

1、Page<> 里面要使用Map<String, Object> 否者查询到的是结果集

2、如果不需要分页的话或者不使page最为分页的集合(不需要统计总数),可以不需要加countQuery,如果需要使用Page,这个必须带上,里面的sql结果是你的数据数量,我这里的value 结果 数量与article 是一样的,所以直接查询的这个表,如果和我需求不一样,请直接使用value的count;

3、最后就是 参数的顺序最好跟sql里面保持一致 在jpa官方文章用的是数字 1、2、3来代替

在弄这个的时候一度想要放弃jpa改用mybatis:sweat_smile:,最后在Stack Overflow找到了问题所在

1、Spring Data and Native Query with pagination

2、jpa 官网文档,坑太多

个人站点

### 如何使用 JPA 实现带条件的分页查询 在 Spring Data JPA 中,可以通过种方式实现带有条件的分页查询。以下是几种常见的方法及其具体实现。 #### 方法一:通过 `PageRequest` 和自定义查询语句 可以利用 `PageRequest` 构建分页请求对象,并结合 JPQL 或原生 SQL 查询来完成复杂条件下的分页操作。 ```java import org.springframework.data.domain.Page; import org.springframework.data.domain.PageRequest; import org.springframework.data.jpa.repository.Query; @Repository public interface UserRepository extends JpaRepository<UserDO, Long> { @Query("SELECT u FROM UserDO u WHERE u.username LIKE %?1% AND u.email LIKE %?2%") Page<UserDO> findByUsernameAndEmail(String username, String email, Pageable pageable); } // 调用示例 int pageNumber = 0; // 当前页码(从0开始) int pageSize = 10; // 每页大小 String sortField = "id"; // 排序字段 String sortOrder = "ASC"; // 排序方向 PageRequest pageRequest = PageRequest.of(pageNumber, pageSize, sortOrder.equalsIgnoreCase("asc") ? Sort.Direction.ASC : Sort.Direction.DESC, sortField); userRepository.findByUsernameAndEmail("%john%", "%example.com%", pageRequest); ``` 此方法适用于简单的条件过滤场景[^1]。 --- #### 方法二:基于 `ExampleMatcher` 的动态条件匹配 如果需要支持更灵活的条件组合,可以借助 `ExampleMatcher` 提供的功能。这种方式无需手动编写复杂的查询逻辑即可满足大部分需求。 ```java import org.springframework.data.domain.Example; import org.springframework.data.domain.ExampleMatcher; import org.springframework.data.domain.Page; import org.springframework.data.domain.Pageable; @Repository public interface UserRepository extends JpaRepository<UserDO, Long> { default Page<UserDO> searchUsersByConditions(UserDO userDO, Pageable pageable) { ExampleMatcher matcher = ExampleMatcher.matching() .withIgnoreNullValues() // 忽略 null 字段 .withIgnoreCase(true) // 启用忽略大小写 .withMatcher("username", ExampleMatcher.GenericPropertyMatchers.contains()) .withMatcher("email", ExampleMatcher.GenericPropertyMatchers.startsWith()); Example<UserDO> example = Example.of(userDO, matcher); return findAll(example, pageable); } } ``` 调用时只需传递一个部分填充的对象实例作为模板: ```java UserDO queryTemplate = new UserDO(); queryTemplate.setUsername("John"); queryTemplate.setEmail("j"); PageRequest pageRequest = PageRequest.of(0, 10, Sort.by(Sort.Direction.ASC, "id")); userRepository.searchUsersByConditions(queryTemplate, pageRequest); ``` 这种方法非常适合处理不确定数量或类型的筛选条件[^2]。 --- #### 方法三:Specification API 进阶版 对于极其复杂的业务逻辑或者无法直接映射到实体类上的特殊规则,则推荐采用 Specifications 技术栈构建更加精细化的查询达式树结构。 首先创建封装好的规格化接口实现类文件specifications.java: ```java import org.springframework.data.jpa.domain.Specification; public class UserSpecifications { public static Specification<UserDO> hasUsernameLike(String keyword){ return (root, criteriaQuery, criteriaBuilder)-> criteriaBuilder.like(root.get("username"), "%" + keyword +"%"); } public static Specification<UserDO> withActiveStatus(Boolean activeFlag){ return (root,criteriaQuery,criteriaBuilder)->{ if(activeFlag !=null && !activeFlag.booleanValue()){ return criteriaBuilder.isNull(root.get("deactivationDate")); }else{ return criteriaBuilder.isNotNull(root.get("deactivationDate")); } }; } } ``` 接着修改repository层代码如下所示: ```java import org.springframework.data.jpa.repository.JpaSpecificationExecutor; @Repository public interface UserRepository extends JpaRepository<UserDO,Long>,JpaSpecificationExecutor<UserDO>{ } @Service @Transactional(readOnly=true) public class UserServiceImpl implements UserService{ @Autowired private final UserRepository userRepository ; public List<UserDTO> getUsersFiltered(Integer pageNo,Integer size,String sortByDirection ,Boolean isActive ){ Pageable paging=PageRequest.of(pageNo,size,(sortByDirection.equals("desc"))?Sort.Direction.DESC:Sort.Direction.ASC,"createdOn"); Specification spec=UserSpecifications.hasUsernameLike("test").and(UserSpecifications.withActiveStatus(isActive)); Page<UserDO> result=userRepository.findAll(spec,paging); return mapToDto(result.getContent()); } } ``` 这种模式下能够轻松应对各种嵌套关系以及跨联结等情况的发生[^4]。 --- ### 总结 以上介绍了三种主流技术路线用于解决实际开发过程中遇到的不同层次难度级别的问题解决方案。开发者可以根据项目具体情况选择最适合自己的那一款工具集来进行编码实践工作当中去应用起来吧!
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值