From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: functional call named notation clashes with SQL feature |
Date: | 2010-05-31 14:26:00 |
Message-ID: | AANLkTin-nD9lXTeCLJNBgAJvRXHWkU3dBUd5LrFKJ35z@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/5/31 Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> --
> 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 | Simon Riggs | 2010-05-31 14:43:20 | Re: PG 9.0 release timetable |
Previous Message | Bruce Momjian | 2010-05-31 14:16:26 | Re: functional call named notation clashes with SQL feature |