Richard Broersma Jr <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
