Skip site navigation (1) Skip section navigation (2)

Re: function_name.parameter_name

From: Darren Duncan <darren(at)darrenduncan(dot)net>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: function_name.parameter_name
Date: 2010-09-08 22:57:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alvaro Herrera wrote:
> Excerpts from Darren Duncan's message of miƩ sep 08 18:29:35 -0400 2010:
>> Personally I like the idea of developers not always having to be forced to 
>> choose among two equally good names, and making a wrapper function would be 
>> overkill for this feature.
> While I don't agree with the idea of providing extra names that are
> probably mostly going to increase the confusion of someone trying to
> understand such a system, I think this use case would be well covered by
> synonyms.  But these would be defined by a new SQL command, say CREATE
> SYNONYM, not by funny notation on the initial CREATE FUNCTION call.

Yes, and having a more general solution like CREATE SYNONYM is more important to 
have anyway.  My "|" is simply a syntactic shorthand for a special case of 
CREATE SYNONYM, with respect to schema objects, and would parse into the same 
thing.  I don't feel any need now for me to push this shorthand further. -- 
Darren Duncan

In response to


pgsql-hackers by date

Next:From: John AdamsDate: 2010-09-08 23:44:07
Subject: Re: returning multiple result sets from a stored procedure
Previous:From: Alvaro HerreraDate: 2010-09-08 22:34:55
Subject: Re: function_name.parameter_name

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group