| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Darren Duncan <darren(at)darrenduncan(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: function_name.parameter_name |
| Date: | 2010-09-08 22:34:55 |
| Message-ID: | 1283985160-sup-8720@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darren Duncan | 2010-09-08 22:57:03 | Re: function_name.parameter_name |
| Previous Message | Darren Duncan | 2010-09-08 22:29:35 | Re: function_name.parameter_name |