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

Bruce Momjian wrote:
> Peter Eisentraut wrote:
>   
>> On tor, 2010-05-27 at 12:59 -0400, Tom Lane wrote:
>>     
>>>> I think we should fix it now.  Quick thought: maybe we could use
>>>>         
>>> FOR 
>>>       
>>>> instead of AS: select myfunc(7 for a, 6 for b);
>>>>         
>>> I'm afraid FOR doesn't work either; it'll create a conflict with the
>>> spec-defined SUBSTRING(x FOR y) syntax.
>>>       
>> How about
>>
>> select myfunc(a := 7, b := 6);
>>     
>
> One concern I have is that in PL/pgSQL, := and = behave the same, while
> in SQL, they would not.  That might cause confusion.
>
>   

That is a sad wart that we should never have done, IMNSHO (it was before 
my time or I would have objected ;-) ). But beyond that, = is an 
operator in SQL and := is never an operator, IIRC.

cheers

andrew

I doubt there will be much confusion.