Re: <> ALL( ... ) and <> ANY ( ... ) didn't behave as expected

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
Cc: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: <> ALL( ... ) and <> ANY ( ... ) didn't behave as expected
Date: 2007-10-10 18:58:00
Message-ID: 21915.1192042680@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Richard Broersma Jr <rabroersma(at)yahoo(dot)com> writes:
> Can anyone explain why <> ANY() behaves that way it does?

Aside from the responses already given, I'm wondering whether you have
any NULL entries in Children.gender. NULL rows within a NOT IN
subselect tend to produce confusing results ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Broersma Jr 2007-10-10 19:24:38 Re: <> ALL( ... ) and <> ANY ( ... ) didn't behave as expected
Previous Message Merlin Moncure 2007-10-10 18:49:16 preferred way to use PG_GETARG_BYTEA_P in SPI