| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Grzegorz Jaskiewicz" <gj(at)pointblue(dot)com(dot)pl>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: default values for function parameters |
| Date: | 2008-12-11 15:04:42 |
| Message-ID: | 4940D7AA.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> In any case, I'm not wedded to using AS for this, and am happy to
> consider other suggestions. But => isn't acceptable.
How about using a bare equals sign (or the => characters) for
parameter assignment, but require that the parameter name be prefixed
with some special character? (My first thought was a dollar sign, but
that would cause problems in PL/pgSQL, so some other character would
need to be used.) It seems like that could give the parser enough
context to consider the operator as parameter assignment, so it
wouldn't require making it a fully reserved word or preclude other
uses of the operator.
I guess it would preclude the use of whatever character was chosen as
a prefix operator in the context of a parameter list, however; which
might be a fatal flaw to the idea.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-12-11 15:06:00 | Re: WIP: default values for function parameters |
| Previous Message | Greg Stark | 2008-12-11 15:04:13 | Re: posix_fadvise v22 |