From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] Function argument names |
Date: | 2004-01-07 13:48:49 |
Message-ID: | 2337.24.211.141.25.1073483329.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
[transferring to hackers]
Tom Lane said:
> Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> writes:
>> I've implemented function argument names,
>
> I have reviewed and applied this patch, with some editorialization.
>
>> Other languages then pl/pgsql should also work to extend, but I've not
>> looked at that. The langage sql I've planned to look at, but since
>> that language is not as separate as the others I did not want to do it
>> yet.
>
> I am not real sure what support for this should look like in SQL
> functions. From the point of view of a SQL command inside a function,
> it seems very close to a global SQL variable, which is a notion that
> we've always shied away from. The PL languages are more comfortable
> with such things, and should probably get fixed first.
>
It occurred to me that perhaps by analogy with NEW and OLD, we could use
ARGS.foo to refer to a parameter called "foo".
Just a thought - I'd probably accept anything reasonable to get rid of the
ugly $n notation :-)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-01-07 15:02:43 | Re: Bug in new buffer freelist code |
Previous Message | Andrew Dunstan | 2004-01-07 13:29:45 | Re: Brokenness in parsing of pg_hba.conf |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2004-01-07 15:48:21 | Re: add "WITH OIDS" to CREATE TABLE AS |
Previous Message | Tom Lane | 2004-01-07 06:33:42 | Re: Function argument names |