Re: functional call named notation clashes with SQL feature
От | Pavel Stehule |
---|---|
Тема | Re: functional call named notation clashes with SQL feature |
Дата | |
Msg-id | AANLkTin-nD9lXTeCLJNBgAJvRXHWkU3dBUd5LrFKJ35z@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: functional call named notation clashes with SQL feature (Bruce Momjian <bruce@momjian.us>) |
Список | pgsql-hackers |
2010/5/31 Bruce Momjian <bruce@momjian.us>: > Tom Lane wrote: >> So as far as I can tell, no one is opposed to replacing "expr AS name" >> with "name := expr" in the named-parameter syntax. Obviously we had >> better get this done before beta2. Is anyone actually working on the >> code/docs changes? If not, I'll pick it up. > > If we eventually are going to want to support the ANSI standard "=>" > syntax, I am thinking we should just do it now. The larger question is > what justification do we have of not supporting "=>". I am for ANSI stanadard. I afraid so we can do nothing now. First we have to implement substitution of "=>" operator in hstore module. Second we have to mark this operator as deprecated. Maybe we can do it in 9.1 with integration of hstore to core. I would to see any hash table support in core. It can be significant help for PLpgSQL coders. What more - it can work nice with proposed JSON support. Regards Pavel > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers >
В списке pgsql-hackers по дате отправления: