| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Joel Jacobson <joel(at)trustly(dot)com> |
| Subject: | Re: merging some features from plpgsql2 project |
| Date: | 2017-01-08 06:03:51 |
| Message-ID: | CAFj8pRB_J7pAE6=acNO=aWdkRAZkyt3FhpqrUROvs-2JTj1FLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>
>>
>> BTW, I do wish you could change the label of the scope that arguments
>> went into, so that you could use that label to refer to function
>> parameters. If we allowed that it'd perhaps be the best of both worlds:
>> you'd be guaranteed access to all auto variables and parameters, and that
>> access wouldn't need to be tied to the function name (which can be both
>> painful and error prone).
>
>
> We can talk about compiler directive.
>
> PRAGMA auto_variables_label(xxxx) -- require function scope only
>
If we know a list of all auto variables, then it can be on function or
block level - it can create aliases.
Regards
Pavel
>
>>
>> --
>> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
>> Experts in Analytics, Data Architecture and PostgreSQL
>> Data in Trouble? Get it in Treble! http://BlueTreble.com
>> 855-TREBLE2 (855-873-2532)
>>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-01-08 06:56:17 | Re: merging some features from plpgsql2 project |
| Previous Message | Ryan Murphy | 2017-01-08 05:49:03 | Re: Adding type info etc for inheritance errmsg: "child table is missing column ..." |