I wrote:
> Dennis Bjorklund <[EMAIL PROTECTED]> writes:
>> This testcase works in 7.3 but not in 7.4:
>> create table t1 (a int);
>> create table t2 (b int);
>> select * from t1, (select b as a from t2 group by a) as foo;
> Another tweak we could make is to cause findTargetlistEntry() to look
> o
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> On Mon, 5 Apr 2004, Tom Lane wrote:
>> However this could break existing queries that are relying on the
>> non-aliased behavior.
> This would be programs written for 7.4, In 7.3 and older the search order
> was (1), (2) and there was no (3) if I unde
On Mon, 5 Apr 2004, Tom Lane wrote:
> This example strikes me as a good reason why we ought to deprecate and
> eventually remove the capability for GROUP BY to reference output-list
> aliases. This is not legal per SQL spec,
Sticking to the SQL spec is (almost) always good.
> matches. This wou
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> This testcase works in 7.3 but not in 7.4:
> create table t1 (a int);
> create table t2 (b int);
> select * from t1, (select b as a from t2 group by a) as foo;
> ERROR: column "t2.b" must appear in the GROUP BY clause or be used in an
> aggregate f
This testcase works in 7.3 but not in 7.4:
--
create table t1 (a int);
create table t2 (b int);
select * from t1, (select b as a from t2 group by a) as foo;
--
ERROR: column "t2.b" must appear in the GROUP BY cl
