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

From Heikki Linnakangas
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 4BFE1B63.3070708@enterprisedb.com
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: functional call named notation clashes with SQL feature
List pgsql-hackers
On 27/05/10 09:50, Pavel Stehule wrote:
> 2010/5/27 Heikki Linnakangas<heikki.linnakangas@enterprisedb.com>:
>> AFAIU, the standard doesn't say anything about named parameters. Oracle uses
>> =>, but as you said, that's ambiguous with the =>  operator.
>>
>> +1 for FOR.
>
> I don't see any advantage of "FOR".

Any advantage over AS? It doesn't clash with the "foo AS bar" syntax 
that the standard is using for something completely different, as Peter 
pointed out in the original post.

> We can change ir to support new  standard or don't change it.

What new standard?

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Synchronization levels in SR
Next
From: Fujii Masao
Date:
Subject: Re: Synchronization levels in SR