Re: Odd behavior with NULL value - Mailing list pgsql-admin

From Stephan Szabo
Subject Re: Odd behavior with NULL value
Date
Msg-id 20011220191348.Y85038-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Re: Odd behavior with NULL value  (Bruno Wolff III <bruno@[66.92.219.49]>)
List pgsql-admin
On Thu, 20 Dec 2001, Bruno Wolff III wrote:

> On Thu, Dec 20, 2001 at 04:24:33PM -0800,
>   "Bob Smith, Hammett & Edison, Inc." <bsmith@h-e.com> wrote:
> > See example below of using NULL values with type DATE.  It behaves
> > strangely in expressions, "(x <> null)" gives an entirely different
> > result than "not(x = null)".  Is this intended behavior, if so, why?
> > If not, is this a bug?
>
> There is a hack which will be off by default in 7.2 that changes
> 'x = null' into 'x is null' for compatibility with sqlserver.

As a note, I think it was actually for some feature of Access. :)


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Odd behavior with NULL value
Next
From: bsmith@h-e.com (Bob Smith, Hammett & Edison, Inc.)
Date:
Subject: Re: Odd behavior with NULL value