| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jason Turim <jason(at)signalvine(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |
| Date: | 2016-07-14 22:49:59 |
| Message-ID: | CAKFQuwatx-Q5_7MHg8Gp2i+dXF4o_sC5LJG6V8eSxLG-ncoDMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jul 14, 2016 at 6:40 PM, Jason Turim <jason(at)signalvine(dot)com> wrote:
> I see, thanks. Have you all considered making it an error to execute
> correlated queries without table qualifying the column names?
>
Will never happen. I'm not even sure it would be desirable in a
greenfield situation let alone in an established product.
One automated way to handle this would be for a schema-aware static
analyzer to be run on the query in question and point out the discrepancy.
If we ever got something like that into core people could choose this
behavior as part of its configuration. There is quite a bit of room
outside of core for tools of this nature to be of value.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-07-14 22:57:04 | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |
| Previous Message | Jason Turim | 2016-07-14 22:40:56 | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |