Re: "AS" by the syntax of table reference.(8.4 proposal) - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: "AS" by the syntax of table reference.(8.4 proposal)
Date
Msg-id 87lk5vksbo.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: "AS" by the syntax of table reference.(8.4 proposal)  ("Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>)
Responses Re: "AS" by the syntax of table reference.(8.4 proposal)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Hiroshi Saito" <z-saito@guitar.ocn.ne.jp> writes:

> Oops, and,
>>> so we really need to support at least ColId as the allowed set of
>>> column alias names.  (I tried changing the patch to do that, but
>>> got a lot of shift/reduce conflicts, some of which are maybe fixable
>>> but some seem hard to fix.)

I think supporting only IDENT wouldn't be all that much of a loss.

But yeah, c_expr isn't enough. We really need {a,b}_expr sans postfix
expressions. I tried to create something like that earlier and found my bison
grammar foo a bit rusty.

Hm. I wonder if we could do a hack where we parse the a_expr ColId as a
regular a_expr and then check for that in the target_el rule or in parse
analysis and pull the ColId out.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about
EnterpriseDB'sPostgreSQL training!
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: "AS" by the syntax of table reference.(8.4 proposal)
Next
From: Tom Lane
Date:
Subject: Re: "AS" by the syntax of table reference.(8.4 proposal)