Re: BUG #14514: Bug in Subquery

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: reva(dot)d91(at)gmail(dot)com
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14514: Bug in Subquery
Date: 2017-01-25 15:31:27
Message-ID: CAKFQuwZJ+Wi8E5wP4PZSgFP1mft16Q7kvjStT-MvzhE0M6Avpg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jan 25, 2017 at 12:23 AM, <reva(dot)d91(at)gmail(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 14514
> Logged by: Revathi Dharmalingam
> Email address: reva(dot)d91(at)gmail(dot)com
> PostgreSQL version: 9.3.10
> Operating system: Windows 7/Unix
> Description:
>
> It is ignoring the invalid columns in subquery,Instead of throwing the
> error
> 'Column does not exist'.
>
> (eg):
> select * from emp where (empname,empid,empno) in(selec emname,emid,emno
> from
> em_details)
>
> Note:There is no emno in em_details table.
> ​
>

​Working as designed. The reference to "emno" comes from the "emp" table -
this is what is called a correlated subquery.

David J.​

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-01-25 15:33:45 Re: could not fork autovacuum worker process: No error
Previous Message Tom Lane 2017-01-25 15:29:13 Re: BUG #14514: Bug in Subquery