3sane 发表于 2011-01-30 17:16

DB2里EXISTS和IN除了性能上,NULL的处理也不同

本帖最后由 3sane 于 2011-01-30 17:18 编辑

举例:
建表:
CREATE TABLE T1 (C1 INTEGER ,C2 CHAR(30) );
CREATE TABLE T2 LIKE T1;
插入数据:
INSERT INTO T1 VALUES(2,CURRENT DATE);
INSERT INTO T1 VALUES(3,CURRENT DATE);

INSERT INTO T2 VALUES(1,CURRENT DATE);
INSERT INTO T2 VALUES(2,CURRENT DATE);

这时候用IN 或 EXISTS都没有问题,但是往T2插入:
INSERT INTO T2 VALUES(NULL,'NULL');

执行SELECT * FROM T1 WHERE C1 NOT IN (SELECT C1 FROM T2),没有结果
执行SELECT * FROM T1 A WHERE NOT EXISTS (SELECT 1 FROM T2 WHERE C1=A.C1),结果C1=3出来了

再往T1插入:
INSERT INTO T2 VALUES(NULL,'NULL');

执行SELECT * FROM T1 WHERE C1 NOT IN (SELECT C1 FROM T2),还是没有结果
执行SELECT * FROM T1 A WHERE NOT EXISTS (SELECT 1 FROM T2 WHERE C1=A.C1),结果C1=3和C1 IS NULL出来了

如果说NULL不等于任何值,哪怕NULL和NULL,那么EXISTS可以理解,但是IN又如何解析呢?
页: [1]
查看完整版本: DB2里EXISTS和IN除了性能上,NULL的处理也不同