From: | John McKown <john(dot)archie(dot)mckown(at)gmail(dot)com> |
---|---|
To: | reva(dot)d91(at)gmail(dot)com |
Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14514: Bug in Subquery |
Date: | 2017-01-25 15:23:53 |
Message-ID: | CAAJSdjj4MCa+eVE1nmLsy+f2z526+9vTR8wJiTFAovVh=T2evw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Jan 25, 2017 at 1: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.
>
>
Note: just user, not developer.
I tried to duplicate your error in PostgreSQL 9.5.5 on Fedora Linux 25,
64 bit. I got the expected "column does not exist". Can you try version 9.5
or even 9.6 to see if the bug is squashed in a later Windows version?
--
There’s no obfuscated Perl contest because it’s pointless.
—Jeff Polk
Maranatha! <><
John McKown
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-01-25 15:25:50 | Re: BUG #14512: Backslashes in LIKE |
Previous Message | David G. Johnston | 2017-01-25 15:11:15 | Re: BUG #14512: Backslashes in LIKE |