BUG #3937: timestamp null value comparison in subquery using IN/NOT IN

From: "Jan Mate" <mate(at)yeea(dot)eu>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3937: timestamp null value comparison in subquery using IN/NOT IN
Date: 2008-02-06 20:15:59
Message-ID: 200802062015.m16KFxQo017080@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 3937
Logged by: Jan Mate
Email address: mate(at)yeea(dot)eu
PostgreSQL version: 8.2.6
Operating system: Linux & Mac OS X
Description: timestamp null value comparison in subquery using IN/NOT
IN
Details:

Comparison between null and timestamp null value is not correct.

Try this example:

CREATE TABLE _test ("timestamp" timestamp);
INSERT INTO _test (timestamp) VALUES (null);

SELECT 1 WHERE (null) NOT IN (SELECT * FROM _test);
?column?
----------
(0 rows)

SELECT 1 WHERE (null) IN (SELECT * FROM _test);
?column?
----------
(0 rows)

Is there any other way to compare the subquery result (using IN or NOT IN)
with null value?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-02-06 23:28:59 Re: BUG #3937: timestamp null value comparison in subquery using IN/NOT IN
Previous Message Tom Lane 2008-02-06 16:26:16 Re: Vers. 8.3.0: "make check" fails dismally