SQL KEEP 窗口函数等价改写案例

一哥们出条sql题给我玩,将下面sql改成不使用keep分析函数的写法。

复制代码
select deptno,
       ename,
       sal,
       hiredate,
       min(sal) keep(dense_rank first order by hiredate) over(partition by deptno) min_sal,
       max(sal) keep(dense_rank last order by hiredate) over(partition by deptno) max_sal
  from emp;

我一开始改错了,被这哥们喷菜鸡,我草。

复制代码
-- 错误等价改写,逻辑不等价
with x as (
select e1.deptno,
       e1.ename,
       e1.sal,
       e1.hiredate,
       row_number() over (partition by DEPTNO order by HIREDATE) rn_first,
       row_number() over (partition by DEPTNO order by HIREDATE DESC) rn_last
from EMP e1)
select
    e.deptno,
    e.ename,
    e.sal,
    e.hiredate,
    x1.SAL,
    x2.SAL
from emp e
    inner join x x1 on e.DEPTNO = x1.DEPTNO and x1.rn_first = 1
    inner join x x2 on e.DEPTNO = x2.DEPTNO and x2.rn_last = 1;

我换了张表测试下,发现上面改写是逻辑有问题,如果同一个组内有相同日期的 ,分组字段内有NULL值的,确实会导致SQL结果集不一致。

复制代码
-- 将EMP表替换成EMPLOYEES,如果使用上面等价改写就错误了。
select DEPARTMENT_ID,
       FIRST_NAME,
       SALARY,
       HIRE_DATE,
       min(SALARY) keep(dense_rank first order by HIRE_DATE) over(partition by DEPARTMENT_ID) min_sal,
       max(SALARY) keep(dense_rank last order by HIRE_DATE) over(partition by DEPARTMENT_ID) max_sal
from EMPLOYEES;

最终等价改写的SQL,增加了分组字段内有NULL值的逻辑 ,和处理一个组内有相同日期的逻辑。

复制代码
select e.DEPARTMENT_ID,
       e.FIRST_NAME,
       e.SALARY,
       e.HIRE_DATE,
       (select MIN_SALARY
        from (select DEPARTMENT_ID, MIN(SALARY) MIN_SALARY
              from (select DEPARTMENT_ID,
                           SALARY,
                           HIRE_DATE,
                           dense_rank() over (PARTITION BY DEPARTMENT_ID ORDER BY HIRE_DATE) RN
                    from EMPLOYEES)
              WHERE RN = 1
              GROUP BY DEPARTMENT_ID) e1
        where case when e1.DEPARTMENT_ID is null then 99999 else e1.DEPARTMENT_ID end = case when e.DEPARTMENT_ID is null then 99999 else e.DEPARTMENT_ID end) a_min,
       (select MAX_SALARY
        from (select DEPARTMENT_ID, MAX(SALARY) MAX_SALARY
              from (select DEPARTMENT_ID,
                           SALARY,
                           HIRE_DATE,
                           dense_rank() over (PARTITION BY DEPARTMENT_ID ORDER BY HIRE_DATE DESC) RN
                    from EMPLOYEES)
              WHERE RN = 1
              GROUP BY DEPARTMENT_ID) e1
        where case when e1.DEPARTMENT_ID is null then 99999 else e1.DEPARTMENT_ID end = case when e.DEPARTMENT_ID is null then 99999 else e.DEPARTMENT_ID end ) a_max
FROM EMPLOYEES e;

差集比较后是等价的:

相关推荐
freejackman9 小时前
【实战二】字段级血缘追踪:拆解 AST 迷局,精准穿透函数链与子查询
大数据·数据库·sql
骑着蜗牛撵大象3271 天前
MySQL 8.0 迁移后 SQL 变慢:执行计划里 3 类被忽略的成本差异
android·数据库·sql·mysql·优化器·执行计划
zhengfei6112 天前
Go-fastdfs /reload 未授权访问: 有效PoC
数据库·sql
大维2 天前
DBX 实测:从 SQLite 查询到 MiniMax-M3 自然语言生成 SQL
数据库·sql·sqlite
景煜拾年2 天前
InnoAI SQL 助手
运维·数据库·笔记·sql
Decay__3 天前
22_MySQL 运维自动化平台 —— 部署编排 + 监控 + 巡检 + 告警 + 工单闭环一体化
运维·数据库·sql·mysql·架构
FungLeo3 天前
成为全栈·基础补充·数据库索引:为什么加了索引还是慢
mysql·postgresql·sqlite·sql优化·数据库索引·成为全栈
Decay__3 天前
21_MySQL 优化案例集 —— 慢 SQL 优化、索引重构与参数调整收益对比
运维·数据库·sql·mysql·架构
挖掘狂人3 天前
MySQL 深分页优化:limit 100000, 10 慢在哪,怎么救
后端·sql·mysql
codigger3 天前
MySQL 深分页优化:limit 100000, 10 慢在哪,怎么救
数据库·sql·mysql·程序员