Re: comparing NEW and OLD (any good this way?)

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: comparing NEW and OLD (any good this way?)
Date: 2009-08-13 22:53:49
Message-ID: 407d949e0908131553p1e877b7s76436b09561d26c2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Aug 13, 2009 at 11:44 PM, Daniel Verite<daniel(at)manitou-mail(dot)org> wrote:
>> In other discussions about similar issues I've said that the expression:
>>
>>   ROW(NULL,NULL) IS DISTINCT FROM NULL
>>
>> should evaluate to FALSE.  I still think this is correct and generally
>> useful behavior.
>
> I see no reason to disagree with this. Besides, the fact that
> ROW(NULL,NULL) IS DISTINCT FROM NULL evaluates to true
> while ROW(NULL,NULL) IS NULL also evaluates to true
> looks quite puzzling to me.

Why is this thread still going on? What does the spec say we should be
doing and are we violating it in any of these cases?

--
greg
http://mit.edu/~gsstark/resume.pdf

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Emanuel Calvo Franco 2009-08-13 23:01:25 Re: plperl function
Previous Message Daniel Verite 2009-08-13 22:44:41 Re: comparing NEW and OLD (any good this way?)