| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, "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 20:46:28 |
| Message-ID: | 4942CDA4.9060705@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.
>
>
>
Does that mean the whitespace following the : will be required? (I could
figure it out but brain is otherwise occupied).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-12-12 21:15:52 | So, why shouldn't SET CONSTRAINTS set a transaction snapshot? |
| Previous Message | Alvaro Herrera | 2008-12-12 20:40:01 | Re: psql commands for SQL/MED |