| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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 21:35:52 |
| Message-ID: | 10726.1229117752@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> 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).
Only if what's immediately after the colon is an identifier, and
possibly not even then depending on the client-side context. For
instance psql won't do anything unless the identifier matches one
of its variables. We'd definitely want to document a recommendation
to leave a space there, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2008-12-12 22:02:15 | Re: psql commands for SQL/MED |
| Previous Message | Tom Lane | 2008-12-12 21:29:11 | Re: psql commands for SQL/MED |