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

From Andrew Dunstan
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 4C03E320.1000305@dunslane.net
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
List pgsql-hackers

Bruce Momjian wrote:
> MSSQL?  Are you sure?  This is the example posted in this thread:
>
>     EXEC dbo.GetItemPrice @ItemCode = 'GXKP', @PriceLevel = 5
>
> and it more matches our := syntax than => in its argument ordering.
>   

I think you are seriously confused, or else you are seriously confusing 
me. The => proposal is to have the ordering "param_name => 
passed_value", just as Oracle has, just as MSSQL  has "@param_name = 
passed_value", and just as the := proposal would have "param_name := 
passed_value".

cheers

andrew


pgsql-hackers by date:

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