From: Ed Loehr <eloehr@austin.rr.com>
To: Mike Mascari <mascarm@mascari.com>
Cc: Joseph Shraibman <jks@p1.selectacast.net>
Cc: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] selectecting not null varchars.
Date: Thu, 24 Feb 2000 17:50:21 -0600
Message-ID: <38B5C3BD.64839CD0@austin.rr.com> (raw)
References: <38B58AAE.B28DD6CB@selectacast.net>
<38B58ED8.FDE3E3C7@austin.rr.com>
<38B55346.9156B92D@mascari.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: eloehr@austin.rr.com, mascarm@mascari.com, jks@p1.selectacast.net
Subject: Re: [INTERFACES] selectecting not null varchars.
In-Reply-To: <38B5C3BD.64839CD0@austin.rr.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox