| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Jason Turim <jason(at)signalvine(dot)com>, "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:57:04 |
| Message-ID: | 20160714225704.GA29609@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
David G. Johnston wrote:
> 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.
The problem is that this is defined by the SQL standard, so we're not at
liberty to change it. The opinion of several people is that it would be
safer to require the qualification. If this were a green field I'm sure
we'd do it differently.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Turim | 2016-07-14 23:35:55 | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |
| Previous Message | David G. Johnston | 2016-07-14 22:49:59 | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |