On Mon, 27 Sep 2004, Mike Rylander wrote:
> On Sun, 26 Sep 2004 20:16:52 +0200, David Helgason <david(at)uti(dot)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.
In response to
pgsql-general by date
|Next:||From: Greg Stark||Date: 2004-09-27 15:17:38|
|Subject: Re: Null comparisons (was Re: checksum)|
|Previous:||From: Andrew Sullivan||Date: 2004-09-27 14:38:14|
|Subject: Re: core dump on select|