Null comparisons (was Re: checksum) - Mailing list pgsql-general

From Stephan Szabo
Subject Null comparisons (was Re: checksum)
Date
Msg-id 20040927074416.C70916@megazone.bigpanda.com
Whole thread Raw
In response to Re: checksum  (Mike Rylander <mrylander@gmail.com>)
Responses Re: Null comparisons (was Re: checksum)  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
On Mon, 27 Sep 2004, Mike Rylander wrote:

> On Sun, 26 Sep 2004 20:16:52 +0200, David Helgason <david@uti.is> wrote:

> > On a similar note, I've found myself wanting an extended '=' operator
> > meaning
> >         (a = b or (a is null and b is null))
> >
>
> Setting 'transform_null_equals' to true in postgresql.conf should do
> what you want.

Unfortunately, it probably won't.  That only changes the explicit token
sequence = NULL into an IS NULL, it won't help if you're doing a=b where a
or b may be NULL.

The original does appear to be equivalent to "not(a is distinct from b)",
although I'm not sure that's necessarily easier to use than the above.

pgsql-general by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: core dump on select
Next
From: Greg Stark
Date:
Subject: Re: Null comparisons (was Re: checksum)