Re: Named arguments in function calls - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Named arguments in function calls
Date
Msg-id 28934.1075069389@sss.pgh.pa.us
Whole thread Raw
In response to Re: Named arguments in function calls  (Dennis Bjorklund <db@zigo.dhs.org>)
Responses Re: Named arguments in function calls  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Dennis Bjorklund <db@zigo.dhs.org> writes:
> I kind of like AS also now after thinking about it. The only reason for => 
> is that oracle used it, nothing else.

Peter Eisentraut pointed out to me that I'd missed a conflicting feature
in SQL99: that spec uses "value AS type" in some function-call contexts.
It's essentially a cast without the CAST() decoration.  (See
<SQL argument list> and <generalized expression>.)

I'm not sure if we'll ever get around to implementing SQL99's ideas
about user-defined types; they seem pretty bizarre.  But it is probably
unwise to select a directly conflicting syntax for parameter names.

So, back to the drawing board ... what else can we use?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Named arguments in function calls
Next
From: Rod Taylor
Date:
Subject: Re: Named arguments in function calls