Re: Odd behavior with NULL value

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.