Re: BUG #4076: "IS NOT NULL (IS NULL)" return wrong answer even where all fields are NULL(or NOT NULL).

From: Tatsuhito Kasahara <kasahara(dot)tatsuhito(at)oss(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4076: "IS NOT NULL (IS NULL)" return wrong answer even where all fields are NULL(or NOT NULL).
Date: 2008-04-02 03:24:58
Message-ID: 47F2FC8A.9070408@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi.

Tom Lane wrote:
>> I think following fix is related..
>> http://archives.postgresql.org/pgsql-committers/2006-09/msg00439.php
>
> Yup, it is. Why are you reporting this?

Document(for 8.1.11) said "A row value is considered not null if it has at
least one field that is not null. ".
http://www.postgresql.org/docs/8.1/static/functions-comparisons.html#AEN13425

But "IS NOT NULL" action seemed that it also evaluate the row is not null
if the row has no field that is not null in such case.

I didn't know the action is valid or invalid ..

So I reported this.

Best regards.
--
NTT OSS Center
Tatsuhito Kasahara

kasahara(dot)tatsuhito(at)oss(dot)ntt(dot)co(dot)jp

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2008-04-02 07:07:07 Re: BUG #4083: Return type of MAX and MIN of a VARCHAR column is TEXT
Previous Message Tom Lane 2008-04-01 18:49:57 Re: Postgre cant start