| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: WIP: default values for function parameters |
| Date: | 2008-12-12 18:05:57 |
| Message-ID: | 7862.1229105157@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> On Fri, Dec 12, 2008 at 10:06:30AM -0500, Tom Lane wrote:
>> Hmm ... actually, ecpg might be a problem here anyway. I know it has
>> special meaning for :name, but does it allow space between the colon
>> and the name? If it does then the colon syntax loses. If it doesn't
> No. Here's the lexer rule:
> <SQL>:{identifier}((("->"|\.){identifier})|(\[{array}\]))*
> No space possible between ":" and {identifier}.
Excellent. I checked that psql's colon-variable feature behaves the
same. So it looks like the proposed "name: value" syntax would indeed
not break any existing features. Barring better ideas I think we should
go with that one.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-12-12 18:07:10 | Re: benchmarking the query planner |
| Previous Message | Tom Lane | 2008-12-12 18:02:34 | Re: benchmarking the query planner |