Re: Out parameters handling - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Out parameters handling
Date
Msg-id 14100.1236443574@sss.pgh.pa.us
Whole thread Raw
In response to Re: Out parameters handling  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Out parameters handling  (Gregory Stark <stark@enterprisedb.com>)
Re: Out parameters handling  (Rod Taylor <rod.taylor@gmail.com>)
Re: Out parameters handling  (Robert Haas <robertmhaas@gmail.com>)
Re: Out parameters handling  (Marko Kreen <markokr@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Sat, Mar 7, 2009 at 9:08 AM, Rod Taylor <rod.taylor@gmail.com> wrote:
>> It wouldn't be so bad if you could assign internal and external column names.

> This is a good point.  Uglifying the parameter names is sort of OK for
> input parameters, but is much more annoying for output parameters.

How much of this pain would go away if we changed over to the arguably
correct (as in Or*cle does it that way) scoping for names, wherein the
parser first tries to match a name against column names of tables of the
current SQL statement, and only failing that looks to see if they are
plpgsql variables?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Out parameters handling
Next
From: Tom Lane
Date:
Subject: Re: small parallel restore optimization