Message-ID: <50DE0CFD.6060508@gmx.net>
Date: Fri, 28 Dec 2012 16:19:57 -0500
From: Peter Eisentraut <peter_e@gmx.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Pavel Stehule <pavel.stehule@gmail.com>
CC: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: proposal: ANSI SQL 2011 syntax for named parameters
References: 
 <CAFj8pRD82DOVWYqN5vQ-4OEZu3jK-B5mFDMXJ4kKqGTV0sGjOw@mail.gmail.com>
In-Reply-To: 
 <CAFj8pRD82DOVWYqN5vQ-4OEZu3jK-B5mFDMXJ4kKqGTV0sGjOw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 12/28/12 11:22 AM, Pavel Stehule wrote:
> I am not sure, but maybe is time to introduce ANSI SQL syntax for
> functions' named parameters
> 
> It is defined in ANSI SQL 2011
> 
>  CALL P (B => 1, A => 2)
> 
> instead PostgreSQL syntax CALL ( B := 1, A := 2)

I agree it's probably time.

> * should we support both - probably yes

yes

> * how long time we will support pg syntax? - 2..5..ever years
> 
> * when we mark pg syntax as obsolete?
> 
> * when we remove pg syntax?

The := syntax was introduced in 9.0, so it is by now well entrenched.  I
don't think we should remove it at all any time soon.

As for documentation, just state how it is.  The standard syntax is =>,
but because of $various_issues, older versions only support :=.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers