| From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQL-Invoked Procedures for 8.1 |
| Date: | 2004-10-08 05:19:45 |
| Message-ID: | Pine.LNX.4.58.0410081518580.23795@linuxworld.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 8 Oct 2004, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > I'll give you an example why not:
>
> > CALL some_sp ( user IS 19, session IS NULL );
>
> > However, Tom, couldn't AS confuse the parser when used to call a named
> > function in a SELECT clause?
>
> I don't think so. We are talking about
>
> SELECT f(42 AS a, col1 AS b) AS collabel FROM ...
>
> Certainly there's no ambiguity to a person in this: param name AS's are
> inside parens, collabel AS's are not. I believe that bison would deal
> with this handily ... but I have to admit I've not actually tried to
> make the grammar changes for it.
A quick hack on bison confirms that this doesn't generate any conflicts
(as long as you don't add a_expr AS a_expr to a_expr :-)).
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-08 05:19:58 | Re: SQL-Invoked Procedures for 8.1 |
| Previous Message | Tom Lane | 2004-10-08 05:15:45 | Re: SQL-Invoked Procedures for 8.1 |