| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, 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 18:59:39 |
| Message-ID: | 162867790911151059v11cc86a1i82b341b386a7bee7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/11/15 Greg Stark <gsstark(at)mit(dot)edu>:
> On Sun, Nov 15, 2009 at 6:42 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> Personally, I like $var, but @var would be okay, and @@var is acceptable. But I'm JAPH, so my biases should be obvious.
>>
>> @var or @@var should be a break for people from MySQL. @var are r/w in
>> MySQL and @@var are global in T-SQL. So people could be confused.
>
> Besides, do we think MySQL and T-SQL are the heights of good language design?
>
sure no. But same arguments against to :var should be used to @var.
pgscript use it. I don't know the best semantic. But I am not happy
from this proposals. I don't see any consistency.
Pavel
>
> --
> greg
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2009-11-15 18:59:40 | Re: named parameters in SQL functions |
| Previous Message | Brendan Jurd | 2009-11-15 18:58:05 | Re: named parameters in SQL functions |