From: | Rod Taylor <rod(dot)taylor(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Asko Oja <ascoja(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Out parameters handling |
Date: | 2009-03-07 14:08:07 |
Message-ID: | 751261b20903070608n5443c865m49e234f421218f50@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
It wouldn't be so bad if you could assign internal and external column names.
Within the function you call the column "v_foo" but the caller of the
function receives column "foo" instead.
OUT v_foo varchar AS "foo"
Another alternative is requiring a prefix like plout for the
replacement to occur:
( OUT foo varchar )
BEGIN
SELECT foo.somename INTO plout.foo FROM foo WHERE id = 10;
RETURN NEXT;
RETURN;
END;
On Sat, Mar 7, 2009 at 8:50 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Mar 6, 2009 at 8:44 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> Robert,
>>
>> Thing is, anybody can institute their own naming convention. I've long used
>> v_ as a prefix. Allowing : would save me some keystrokes, but that's about
>> it.
>>
>> --Josh
>
> True... but there doesn't seem to be any shortage of people who are
> annoyed by the current behavior. Maybe we should all just learn to
> live with it.
>
> ...Robert
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-03-07 16:11:30 | Re: Out parameters handling |
Previous Message | hugocoolens | 2009-03-07 13:51:21 | field with single quote no longer works in 8.3.5 |