Re: BUG #13336: Unexpected result from invalid query

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christian Ullrich <chris(at)chrullrich(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13336: Unexpected result from invalid query
Date: 2015-05-23 01:14:49
Message-ID: 21081.1432343689@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christian Ullrich <chris(at)chrullrich(dot)net> writes:
> Hm. That makes some sense, I guess. But is that true even if the reference in the subquery is not explicitly qualified? "SELECT foo FROM test_table2" looks to me like it refers to that table pretty unequivocally.

This behavior is required by the SQL standard ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Paragon Corporation 2015-05-23 02:47:18 Re: BUG #13334: PostGIS 2.2 crash in topology (array_contain_compare)
Previous Message Christian Ullrich 2015-05-23 00:31:10 Re: BUG #13336: Unexpected result from invalid query