| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ryan Bradetich <rbradetich(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(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-08 23:36:51 |
| Message-ID: | 5734.1236555411@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ryan Bradetich <rbradetich(at)gmail(dot)com> writes:
> This is one of the things I wanted to start looking at for 8.5.
> My idea was to optionally use : or @ (not sure which is more popular) to
> specify this token is only a variable.
This whole line of thought is really a terrible idea IMHO. plpgsql is
supposed to follow Oracle's pl/sql syntax, not invent random syntax of
its own. I believe that 80% of the problems here are occurring because
we used a crude substitution method that got the priorities backwards
from the way Oracle does it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-03-09 00:21:08 | Re: postgresql.conf: patch to have ParseConfigFile report all parsing errors, then bail |
| Previous Message | Tom Lane | 2009-03-08 23:29:42 | Re: compiler failures on buildfarm member wombat |