Sender: ed
Message-ID: <38B5C3BD.64839CD0@austin.rr.com>
Date: Thu, 24 Feb 2000 17:50:21 -0600
From: Ed Loehr <eloehr@austin.rr.com>
MIME-Version: 1.0
To: Mike Mascari <mascarm@mascari.com>
CC: Joseph Shraibman <jks@p1.selectacast.net>,
	"pgsql-interfaces@postgreSQL.org" <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] selectecting not null varchars.
References: <38B58AAE.B28DD6CB@selectacast.net>
	<38B58ED8.FDE3E3C7@austin.rr.com> <38B55346.9156B92D@mascari.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mike Mascari wrote:
> 
> Someone wrote:
> >
> > Joseph Shraibman wrote:
> > >
> > >  select * from directory where h != null  ;
> > > ... gets you this:
> > > ERROR:  parser: parse error at or near ";"
> >
> > Postgresql's SQL "not equal" operator is "<>"...Try this:
> >
> >         select * from directory where h <> null;
> 
> Does that work?

No, it does not work.  Whoever said that must've not had their
afternoon nap.

> I remember when the equality with NULL was added
> because of non-compliant queries being generated from Access. I
> didn't know inequality was implemented as well. Formal SQL is:
> 
> SELECT * FROM directory WHERE h IS NOT NULL;

You are right.  That guy was asleep.  [Mea culpa...]

Cheers,
Ed Loehr