From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: functional call named notation clashes with SQL feature |
Date: | 2010-05-31 15:07:15 |
Message-ID: | AANLkTilMyzZE71JhZXHqPGiygypleSLjFOUHX70ncIlS@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/5/31 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> 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 "=>".
>
> Not breaking hstore, as well as any third-party modules that might be
> using that operator name. Did you not absorb any of the discussion
> so far?
>
can we search thise applications? I know only about hstore module. We
can ask people who use it in own applications. But every major version
of PostgreSQL can breaks compatibility - like 9.0 with variable names
in plpgsql.
Regards
Pavel
> regards, tom lane
>
> --
> 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 | Tom Lane | 2010-05-31 15:08:35 | Re: PG 9.0 release timetable |
Previous Message | Tom Lane | 2010-05-31 14:59:15 | Re: functional call named notation clashes with SQL feature |