not in在结果集有null值的时候失效

问题描述

一次碰上测试提出的bug是:新增了一条收费规则之后,另一个关联的功能就查不出数据了,经过排查发现是当not in在子查询有null的时候,会查不出任何结果。

业务背景

两张表,一张为协议表(agreement),一张为收费规则表(cost_rule),对于每个agreement,可以设定一条收费规则,按照收费规则表中的agreement_id关联,但是可以有一条默认的收费规则(也就是没有指定收费规则的,按照默认规则收费),所以默认规则的agreement_id为null

场景还原
-- 协议表
create table agreement(id bigint primary key auto_increment, agreement_no varchar(20) unique, agreement_name varchar(50));

-- 收费规则表
create table cost_rule(id bigint primary key auto_increment, agreement_id bigint, rate_value decimal(16.8));

-- 插入测试数据
insert into agreement(agreement_no, agreement_name) value('TEST-001', 'AB');
insert into agreement(agreement_no, agreement_name) value('TEST-002', 'CD');
insert into agreement(agreement_no, agreement_name) value('TEST-003', 'EF');
insert into cost_rule(agreement_id, rate_value) value(1, 0.0002);
insert into cost_rule(agreement_id, rate_value) value(2, 0.0003);
-- 在新增收费规则的时候,只能选择还没有设定收费规则的协议
select * 
from agreement
where id not in (
    select agreement_id 
    from cost_rule
)
and id = 3

查询结果:

idagreement_noagreement_name
3TEST-003EF

此时还是能够查询的出结果的,但是当收费规则表中新增一条agreement_id为null的默认收费规则时,结果就不对了:

insert into cost_rule(rate_value) value(0.0003);

查询结果:

idagreement_noagreement_name
NULLNULLNULL

新增之后,查询结果就没有了。

如何处理

要对查询语句进行改进:

-- 1. 子查询增加is not null条件
select * 
from agreement
where id not in (
    select agreement_id 
    from cost_rule
    -- 子查询中增加了is not null条件
    where agreement_id is not null
)
and id = 3

-- 2. 用IFNULL函数将null改为别的结果(一个不可能的值)
select * 
from agreement
where id not in (
    select IFNULL(agreement_id, -1)
    from cost_rule
)
and id = 3
  • 1
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
场景一: 确认1.碰到了一个一个非常慢的SQL server语句,发现是变量查询时很慢 SQL语句: DECLARE @SN VARCHAR(12) SET @SN = '30F335CD0045' SELECT [Mac2] FROM SF_Cp_Detail WHERE [Mac2] = @SN 确认2.查看索引是:唯一非聚集索引 CREATE UNIQUE NONCLUSTERED INDEX [IX_SF_CP_Detail_MAC2] ON [dbo].[SF_Cp_Detail] ( [Mac2] ASC ) WHERE ([MAC2]'' AND [MAC2] IS NOT NULL) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) GO 确认3.执行计划如下: 执行计划 SET STATISTICS IO ON ; (0 行受影响) Table 'SF_Cp_Detail'. Scan count 33, logical reads 1267942, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0. 场景二: 为什么用不到索引IX_SF_CP_Detail_MAC2]呢? 尝试1: 把唯一非聚集索引改为非聚集索引, Done,用到索引了. Drop index ……. CREATE NONCLUSTERED INDEX [IX_SF_Cp_Detail_Mac2] ON [dbo].[SF_Cp_Detail] ( [Mac2] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) GO 尝试2: 可是还需要验证唯一性怎么办呢? 试了半天未达到目标, 根据别人提示, 恢复唯一非聚集 CREATE UNIQUE NONCLUSTERED INDEX [IX_SF_CP_Detail_MAC2] ON [dbo].[SF_Cp_Detail] ( [Mac2] ASC ) WHERE ([MAC2]'' AND [MAC2] IS NOT NULL) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) GO 然后 修改查询: DECLARE @SN VARCHAR(12) SET @SN = '30F335CD0045' SELECT [Mac2] FROM SF_Cp_Detail WHERE [Mac2] = @SN option (recompile) 预计查询计划 看样子不行, 但是,看一下实际查询计划: OK ,Done,可以了. 尝试3. 但是我不可能去每个程序加option (recompile)呀, 而且随着数据量的增大,每次重新编译索引, 本身就导致SQL语句变慢. 最终解决方案: 唯一非聚集索引留着, 再添加一个 非聚集索引,保留两个索引, 终于搞定了. CREATE UNIQUE NONCLUSTERED INDEX [IX_SF_CP_Detail_MAC2] ON [dbo].[SF_Cp_Detail] ( [Mac2] ASC ) WHERE ([MAC2]'' AND [MAC2] IS NOT NULL) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING =

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值