From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "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-11 08:58:49 |
Message-ID: | 162867790812110058l84fac53la206211f8da4702d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2008/12/10 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> 2008/12/10 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
>>> next argument - if we accept AS for param names, then we introduce
>>> nonconsistent behave with SQL/XML functions.
>>
>>> select xmlforest(c1, c2 as foo, c3) -- there foo isn't doesn't mean
>>> "use it as param foo",
>>
>> It could be read as meaning that, I think.
>>
>> In any case, I'm not wedded to using AS for this, and am happy to
>> consider other suggestions.
what do you thing about?
select fce(p1,p2,p3, SET paramname1 = val, paramname2 = val)
example
select dosome(10,20,30, SET flaga = true, flagb = false)
regards
Pavel Stehule
>
> me too
>
> regards
> Pavel Stehule
>
> But => isn't acceptable.
>>
>> regards, tom lane
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-12-11 09:29:05 | Re: Sync Rep: First Thoughts on Code |
Previous Message | Simon Riggs | 2008-12-11 08:55:24 | Re: Sync Rep: First Thoughts on Code |