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: | 4C8814BF.7040009@darrenduncan.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | John Adams | 2010-09-08 23:44:07 | Re: returning multiple result sets from a stored procedure |
Previous Message | Alvaro Herrera | 2010-09-08 22:34:55 | Re: function_name.parameter_name |