Skip site navigation (1) Skip section navigation (2)

Re: functional call named notation clashes with SQL feature

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: functional call named notation clashes with SQL feature
Date: 2010-05-31 14:59:15
Message-ID: 12885.1275317955@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2010-05-31 15:07:15
Subject: Re: functional call named notation clashes with SQL feature
Previous:From: Simon RiggsDate: 2010-05-31 14:43:20
Subject: Re: PG 9.0 release timetable

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group