| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jan Mate" <mate(at)yeea(dot)eu> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #3937: timestamp null value comparison in subquery using IN/NOT IN |
| Date: | 2008-02-06 23:28:59 |
| Message-ID: | 19919.1202340539@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Jan Mate" <mate(at)yeea(dot)eu> writes:
> Comparison between null and timestamp null value is not correct.
No, it's your expectations that are not correct. Null is not "equal to"
null --- in fact both the queries you show will evaluate the WHERE
clause as null (unknown).
> Is there any other way to compare the subquery result (using IN or NOT IN)
> with null value?
Don't try to use null as a normal data value. Sooner or later you'll
always regret it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | cgriffo | 2008-02-07 00:45:08 | BUG #3938: Row-wise comparison fails |
| Previous Message | Jan Mate | 2008-02-06 20:15:59 | BUG #3937: timestamp null value comparison in subquery using IN/NOT IN |