| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | "David E(dot) Wheeler" <david(dot)wheeler(at)pgexperts(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: function_name.parameter_name | 
| Date: | 2010-09-07 18:39:33 | 
| Message-ID: | AANLkTi=-QPp1BBayaeTcis098K3_XjYA8DV90t3Qw7Fu@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Hi,
On 7 September 2010 20:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> How does $subject differ from what we already do?  See
> http://www.postgresql.org/docs/9.0/static/plpgsql-structure.html
So will it be possible to do things like this?
1.
CREATE FUNCTION func_name(arg_name text) RETURNS integer AS $$
BEGIN
    RAISE INFO '%', func_name.arg_name;
...
2.
CREATE FUNCTION func_name() RETURNS integer AS $$
DECLARE
    var_name text := 'bla';
BEGIN
    RAISE INFO '%', func_name.var_name;
...
3.
CREATE FUNCTION func_very_very_very_very_long_name() RETURNS integer AS $$
<< func_alias >>
DECLARE
    var_name text := 'bla';
BEGIN
    RAISE INFO '%', func_alias.var_name;
...
-- 
Sergey Konoplev
Blog: http://gray-hemp.blogspot.com /
Linkedin: http://ru.linkedin.com/in/grayhemp /
JID/GTalk: gray(dot)ru(at)gmail(dot)com / Skype: gray-hemp / ICQ: 29353802
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-09-07 18:54:47 | Re: UTF16 surrogate pairs in UTF8 encoding | 
| Previous Message | David Fetter | 2010-09-07 18:39:01 | "Freezing" per-role settings |