| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: named parameters in SQL functions |
| Date: | 2009-11-15 18:16:49 |
| Message-ID: | 603c8f070911151016u2fe82a8ap81b01357c30f97a5@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Nov 15, 2009 at 12:37 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> At Tom's suggestion I am looking at allowing use of parameter names in SQL
> functions instead of requiring use of $1 etc. That raises the question of
> how we would disambiguate a parameter name from a column name. Essentially,
> ISTM, we could use some special marker such as @ (c.f. SQL Server) or :
> (c.f. ecpg) or else we could have some rule that says which name takes
> precedence. I think I prefer a special marker, other things being equal. Is
> there a standard on this?
We could also just throw an error if there is any ambiguity. I kind
of like the idea of a special marker for both SQL and PL/pgsql, but
Tom has been negative on that idea in the past.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-11-15 18:19:04 | Re: named parameters in SQL functions |
| Previous Message | Robert Haas | 2009-11-15 18:15:06 | Re: Summary and Plan for Hot Standby |