| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Matthew Draper <matthew(at)trebex(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Allow SQL-language functions to reference parameters by parameter name |
| Date: | 2011-03-26 13:41:46 |
| Message-ID: | 762095B9-DF7A-465F-8826-B79B085DFEFE@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 25, 2011, at 11:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If this were PL/perl, or PL/almost-anything-except-SQL, I could get
> behind such a proposal. But it's not, it's SQL; and SQL doesn't do
> things that way. SQL's idea of disambiguation is qualified names.
>
> And even more to the point: to the extent you think that weird syntax
> might be a suitable solution, you have to keep in mind that the SQL
> committee could take over any such syntax at the drop of a hat.
> See the recent unpleasantness concerning => ...
You can't be guaranteed that they won't standardize something incompatible no matter what we do. We could choose to do it as you've proposed and they could then standardize some weird syntax - the => is a fairly relevant example of exactly that.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2011-03-26 14:30:38 | Lock problem with autovacuum truncating heap |
| Previous Message | Simon Riggs | 2011-03-26 10:16:36 | Re: race condition in sync rep |