| From: | Jason Turim <jason(at)signalvine(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Subject: | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |
| Date: | 2016-07-14 23:35:55 |
| Message-ID: | CAHXPbemAmjNHdutK=Bb-bk1zyGAS9sC87o_pwOtNrvn5weX-KQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thanks again, it's very clear now
On Jul 15, 2016 7:57 AM, "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> wrote:
> 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 | David G. Johnston | 2016-07-14 23:42:48 | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |
| Previous Message | Alvaro Herrera | 2016-07-14 22:57:04 | Re: BUG #14250: Error in subquery fails silently and parent query continues to execute |