Re: <> ALL( ... ) and <> ANY ( ... ) didn't behave as expected - Mailing list pgsql-general

From Tom Lane
Subject Re: <> ALL( ... ) and <> ANY ( ... ) didn't behave as expected
Date
Msg-id 21915.1192042680@sss.pgh.pa.us
Whole thread Raw
In response to <> ALL( ... ) and <> ANY ( ... ) didn't behave as expected  (Richard Broersma Jr <rabroersma@yahoo.com>)
List pgsql-general
Richard Broersma Jr <rabroersma@yahoo.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

pgsql-general by date:

Previous
From: "Merlin Moncure"
Date:
Subject: preferred way to use PG_GETARG_BYTEA_P in SPI
Next
From: Richard Broersma Jr
Date:
Subject: Re: <> ALL( ... ) and <> ANY ( ... ) didn't behave as expected