| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Marko Kreen <markokr(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Rod Taylor <rod(dot)taylor(at)gmail(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-13 17:18:22 |
| Message-ID: | 12335.1236964702@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>>> 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.
Well, we have boatloads of bug reports that say you're wrong on that,
not to mention the Oracle precedent.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2009-03-13 18:06:26 | hstore improvements? |
| Previous Message | Tom Lane | 2009-03-13 14:15:31 | DTrace probes broken in HEAD on Solaris? |