分页问题

### 使用版本(未按照模板填写直接删除)

- jdk版本(带上尾号):  1.8.0_202
- 框架版本(项目启动时输出的版本号): RuoYi-Flowable-Plus Application Version: 0.8.3  (v2.7.11)
在Mapper.xml中自己写了一个比较复杂的SQL,不分页的。功能正常，因为数据量太大，加载时间过慢，想用分页方式来实现快速加载，现在有问题是不知道怎样用默认框架实现分页功能。代码如下：
1、Mapper.xml中的代码：
<select id="get67prabill" parameterType="Map" resultMap="PraybillResult">
        select   pb.cpraybillid,pbb.cpraybill_bid,pb.vpraycode,  iv.invcode,  iv.invname ,  iv.invspec ,
            pbb.vdef8 as material,  me.measname,  pbb.nsuggestprice,  pbb.npraynum,  pb.vdef20 as purprocess,  pbb.crowno,
            pb.dauditdate,  su.user_name as ncusername,  gs.unitname as unitshortname,  pb.vmemo,  bs1.jobcode  || bs1.jobname as  jobname,
            wmsys.wm_concat(  gs.unitshortname  || bdre.deptname  || sure.user_name  || reb.nnum  || me.measname  || ' ') as plansource,
            bs.jobcode  || bs.jobname  || ' ' as reqinformation,'67' as syscode,gs.pk_corp
        FROM po_praybill_b pbb
        INNER JOIN po_praybill pb ON pb.cpraybillid = pbb.cpraybillid
        INNER JOIN bd_corp gs ON gs.pk_corp = pbb.pk_corp
        LEFT JOIN bd_invbasdoc iv ON pbb.cbaseid = iv.pk_invbasdoc
        LEFT JOIN bd_measdoc me ON me.pk_measdoc = iv.pk_measdoc
        LEFT JOIN sm_user su ON su.cuserid = pb.coperator
        LEFT JOIN po_requireapp_b reb ON reb.csourcebid2 = pbb.cpraybill_bid
        LEFT JOIN po_requireapp re ON re.crequireappid =reb.crequireappid
        LEFT JOIN sm_user sure  ON sure.cuserid = re.coperator
        LEFT JOIN bd_deptdoc bdre ON bdre.pk_deptdoc = reb.capplydeptid
        LEFT JOIN bd_jobmngfil bm ON bm.pk_jobmngfil = reb.cprojectid
        LEFT JOIN bd_jobbasfil bs ON bs.pk_jobbasfil = bm.pk_jobbasfil
        LEFT JOIN bd_jobmngfil bm1 ON bm1.pk_jobmngfil = pbb.cprojectid
        LEFT JOIN bd_jobbasfil bs1 ON bs1.pk_jobbasfil = bm1.pk_jobbasfil
        WHERE pb.dr = 0 AND pbb.dr = 0
        <trim>
            <if test="pkCorp != null ">
              AND pb.pk_corp = #{pkCorp}
            </if>
            <if test="invcode != null and invcode !=''">
                AND iv.invcode like #{invcode}
            </if>
            <if test="vpraycode != null and vpraycode !=''">
                AND pb.vpraycode like  #{vpraycode}
            </if>
        </trim>
          and  (pbb.vdef9 is null or  pbb.vdef9='')
          AND pbb.npraynum - NVL(pbb.naccumulatenum, 0) > 0
        AND pb.ibillstatus = 3 AND pb.dauditdate <![CDATA[ >= ]]>#{startDate} AND pb.dauditdate <![CDATA[ <= ]]>#{endDate}

AND pbb.cbaseid IN
            (
                SELECT inv.pk_invbasdoc
                FROM bd_invbasdoc inv
                WHERE pk_invcl IN
                (
                    SELECT cl.resource_data_id
                    FROM sm_power_invcl cl
                    WHERE (cl.pk_corp = '0001'
                    OR cl.pk_corp     = '1002')
                    AND cl.pk_role   IN
                        (SELECT ro.pk_role
                            from sm_user_role ro
                            inner join sm_user tuser on (tuser.cuserid=ro.cuserid)
                            WHERE tuser.user_code = #{userCode}
                            AND (ro.pk_corp  = '0001'
                            OR ro.pk_corp    = '1002')
                        )
                )
            )

group by
        pb.cpraybillid,  pbb.cpraybill_bid,  pb.vpraycode,  iv.invcode,  iv.invname,  iv.invspec,  pbb.vdef8,  me.measname,  pbb.nsuggestprice,  pbb.npraynum,  pb.vdef20,
        pbb.crowno,  pb.dauditdate,  su.user_name,  gs.unitname,  pb.vmemo,  bs1.jobcode  || bs1.jobname ,  bs.jobcode  || bs.jobname,gs.pk_corp
        order by  pb.cpraybillid,  pbb.cpraybill_bid,to_number(pbb.crowno)
    </select>

Mapper类：
  List<PraybillVo> get67prabill(PraybillQuery praybill);
service类：
   public List<PraybillVo>   get67prabill(PraybillQuery praybill){
        return baseMapper.get67prabill(praybill);
    }
 请问我应该怎样调用我自己的mapper中的SQL呢？
谢谢。

KonBAI/RuoYi-Flowable-Plus

内容风险标识

评论 (0)

KonBAI/RuoYi-Flowable-Plus .gitee-modal { width: 500px !important; }

内容风险标识

分页问题

评论 (0)

搜索帮助

KonBAI/RuoYi-Flowable-Plus