Postgres Pro
Downloads
Home   >   mailing lists

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

From Bruno Wolff III
Subject Re: Odd behavior with NULL value
Date
Msg-id 20011220190935.A16538@wolff.to
Whole thread Raw
In response to Odd behavior with NULL value  (bsmith@h-e.com (Bob Smith, Hammett & Edison, Inc.))
Responses Re: Odd behavior with NULL value  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-admin
Tree view 
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.

pgsql-admin by date:

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