Re: functional call named notation clashes with SQL feature - Mailing list pgsql-hackers

From Tom Lane
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 12885.1275317955@sss.pgh.pa.us
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Bruce Momjian <bruce@momjian.us>)
Responses Re: functional call named notation clashes with SQL feature
Re: functional call named notation clashes with SQL feature
Re: functional call named notation clashes with SQL feature
List pgsql-hackers
Bruce Momjian <bruce@momjian.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?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: PG 9.0 release timetable
Next
From: Pavel Stehule
Date:
Subject: Re: functional call named notation clashes with SQL feature