Re: functional call named notation clashes with SQL feature

Поиск
Список
Период
Сортировка
Искать
От
Heikki Linnakangas
Тема
Re: functional call named notation clashes with SQL feature
Дата
в 04:40:46
Msg-id
4BFE21EF.5010106@enterprisedb.com
Ответ на
Список
Дерево обсуждения
functional call named notation clashes with SQL feature Peter Eisentraut <peter_e@gmx.net>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature alvherre <alvherre@commandprompt.com>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Abhijit Menon-Sen <ams@toroid.org>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: functional call named notation clashes with SQL feature Peter Eisentraut <peter_e@gmx.net>
Re: functional call named notation clashes with SQL feature Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: functional call named notation clashes with SQL feature Peter Eisentraut <peter_e@gmx.net>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Joseph Adams <joeyadams3.14159@gmail.com>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Greg Stark <gsstark@mit.edu>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature Joseph Adams <joeyadams3.14159@gmail.com>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Peter Eisentraut <peter_e@gmx.net>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Jan Wieck <JanWieck@Yahoo.com>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Stephen Frost <sfrost@snowman.net>
Re: functional call named notation clashes with SQL feature Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature Josh Berkus <josh@agliodbs.com>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: functional call named notation clashes with SQL feature Dimitri Fontaine <dfontaine@hi-media.com>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Peter Eisentraut <peter_e@gmx.net>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Dimitri Fontaine <dfontaine@hi-media.com>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature Florian Pflug <fgp@phlo.org>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Greg Stark <gsstark@mit.edu>
Re: functional call named notation clashes with SQL feature Tom Lane <tgl@sss.pgh.pa.us>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Andrew Dunstan <andrew@dunslane.net>
Re: functional call named notation clashes with SQL feature Bruce Momjian <bruce@momjian.us>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Dimitri Fontaine <dfontaine@hi-media.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature David Fetter <david@fetter.org>
Re: functional call named notation clashes with SQL feature "David E. Wheeler" <david@kineticode.com>
Re: functional call named notation clashes with SQL feature Robert Haas <robertmhaas@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
Re: functional call named notation clashes with SQL feature Pavel Stehule <pavel.stehule@gmail.com>
On 27/05/10 10:16, Pavel Stehule wrote:
> 2010/5/27 Heikki Linnakangas:
>> On 27/05/10 09:50, Pavel Stehule wrote:
>>>
>>> 2010/5/27 Heikki Linnakangas:
>>>>
>>>> AFAIU, the standard doesn't say anything about named parameters. Oracle
>>>> uses
>>>> =>, but as you said, that's ambiguous with the =>    operator.
>>>>
>>>> +1 for FOR.
>>>
>>> I don't see any advantage of "FOR".
>>
>> Any advantage over AS? It doesn't clash with the "foo AS bar" syntax that
>> the standard is using for something completely different, as Peter pointed
>> out in the original post.
>
> No, standard knows "AS" in different context. In param list standard
> doesn't use keyword "AS".

As Peter pointed out in the original post, according to the standard 
"function(foo AS bar)" means something else than what we have now. 
Please re-read the original post.

>>> We can change ir to support new  standard or don't change it.
>>
>> What new standard?
>
> ANSI SQL 2011

Oh, does that have something to say about named parameters? Is the draft 
publicly available somewhere?

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com

В списке pgsql-hackers по дате отправления
От: Fujii Masao
Дата:
От: Peter Eisentraut
Дата:
FAQ