Re: Oddity with NOT IN - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: Oddity with NOT IN
Date
Msg-id 5894188e-52db-aa1f-dae1-742ded0820a0@joh.to
Whole thread Raw
In response to Oddity with NOT IN  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Oddity with NOT IN  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 2016-08-04 11:23 PM, Jim Nasby wrote:
> I've got a customer that discovered something odd...
>
> SELECT f1 FROM v1 WHERE f2 not in (SELECT bad FROM v2 WHERE f3 = 1);
>
> does not error, even though bad doesn't exist, but

I'm guessing there's a v1.bad?

This is a common mistake, and also why I recommend always table 
qualifying column references when there's more than one table in scope.


.m



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Oddity with NOT IN
Next
From: Andrew Dunstan
Date:
Subject: Re: New version numbering practices