| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oddity with NOT IN |
| Date: | 2016-08-06 16:53:53 |
| Message-ID: | 3cc978cd-9f50-dd65-c9c3-fe2d3c19987a@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/4/16 4:53 PM, Marko Tiikkaja wrote:
> 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.
Well now I feel dumb...
It would be very useful if we had some way to warn users about stuff
like this. Emitting a NOTICE comes to mind.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-08-06 17:03:52 | Re: Oddity with NOT IN |
| Previous Message | Andrew Borodin | 2016-08-06 16:51:20 | Re: Re: GiST optimizing memmoves in gistplacetopage for fixed-size updates [PoC] |