Re: Out parameters handling - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Out parameters handling
Date
Msg-id 49B9BD4D.6040407@agliodbs.com
Whole thread Raw
In response to Re: Out parameters handling  (Marko Kreen <markokr@gmail.com>)
Responses Re: Out parameters handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>> 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?

-1 on this.  If we're to have definite rules, I would prefer that stuff 
gets assumed to be a variable *first*, and then object definitions are 
only examined after the system fails to find a matching variable name.

That priority makes it much easier to debug a function than the Oracle way.

--Josh


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Should SET ROLE inherit config params?
Next
From: Robert Treat
Date:
Subject: Re: Should SET ROLE inherit config params?