Re: Odd behavior with NULL value

From: Bruno Wolff III <bruno(at)[66(dot)92(dot)219(dot)49]>
To: "Bob Smith, Hammett & Edison, Inc(dot)" <bsmith(at)h-e(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Odd behavior with NULL value
Date: 2001-12-21 01:09:35
Message-ID: 20011220190935.A16538@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Dec 20, 2001 at 04:24:33PM -0800,
"Bob Smith, Hammett & Edison, Inc." <bsmith(at)h-e(dot)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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Phill Kenoyer 2001-12-21 01:22:35 Re: Odd behavior with NULL value
Previous Message Bob Smith, Hammett & Edison, Inc. 2001-12-21 00:24:33 Odd behavior with NULL value