| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Andrew Chernow <ac(at)esilo(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: named parameters in SQL functions |
| Date: | 2009-11-15 19:25:36 |
| Message-ID: | 1D6D5B84-4AB8-4738-A156-420DC241F5BC@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 15, 2009, at 11:21 AM, Greg Stark wrote:
> No, that's not the same.
>
> The point is that $ is a perfectly valid SQL identifier character and
> $foo is a perfectly valid identifier. You can always quote any
> identifier (yes, after case smashing) so you would expect if $foo is a
> valid identifier then "$foo" would refer to the same identifier.
> You're introducing a meaning for $foo but saying there's no valid way
> to quote the identifier to get the same thing. And worse, if you do
> quote it you get something else entirely different.
$foo should be killed off as a valid identifier, IMNSHO.
But failing that, some other sigil would be most welcome.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-11-15 19:29:34 | Re: Summary and Plan for Hot Standby |
| Previous Message | Greg Stark | 2009-11-15 19:21:38 | Re: named parameters in SQL functions |