Re: [HACKERS] Parser/planner and column aliases - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] Parser/planner and column aliases
Date
Msg-id 3899B446.FC71BE97@alumni.caltech.edu
Whole thread Raw
In response to Parser/planner and column aliases  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
> I'm running across the behavior that an explicit select as above
> works, but if I try a wildcard expansion (select *...) instead of the
> explicit column listing the planner decides it needs to do some wild
> nested join stuff:

Hmm. Wildcarding like this works:

postgres=# select ty.* from t2 ty (b, c);b | c 
---+---1 | 11 | 22 | 2
(3 rows)

So my problems are maybe just within the parser. Will keep looking at
it...
                     - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Taral
Date:
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Next
From: Peter Mount
Date:
Subject: RE: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL