| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: functional call named notation clashes with SQL feature |
| Date: | 2010-05-27 06:48:53 |
| Message-ID: | AANLkTilLrP7eum-Dh3xDG8DzGsgRJbwylEeW_NcWl23p@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>
>
> I think we should fix it now. Quick thought: maybe we could use FOR instead
> of AS: select myfunc(7 for a, 6 for b); IIRC the standard's mechanism for
> this is 'paramname => value', but I think that has problems because of our
> possibly use of => as an operator - otherwise that would be by far the best
> way to go.
>
What is advice of "FOR" instead "AS"?
it is exactly same.
Regards
Pavel
> cheers
>
> andrew
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-05-27 06:50:18 | Re: functional call named notation clashes with SQL feature |
| Previous Message | Heikki Linnakangas | 2010-05-27 06:26:39 | Re: [spf:guess] Re: ROLLBACK TO SAVEPOINT |