| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Joshua D(dot) Drake <jd(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SYNONYMS (again) |
| Date: | 2011-06-22 22:52:54 |
| Message-ID: | 1308783023-sup-9215@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Joshua D. Drake's message of mié jun 22 15:37:17 -0400 2011:
> Per:
>
> http://archives.postgresql.org/pgsql-hackers/2010-11/msg02043.php
>
> It seems we did come up with a use case in the procpid discussion. The
> ability to change the names of columns/databases etc, to handle the
> fixing of bad decision decisions during development over time.
>
> Thoughts?
Let's start with what was discussed and supported in that thread, that
is, databases. It seems less clear that columns are widely believed to
be a good idea to have synonyms for. Besides, synonyms for databases
should be reasonably simple to implement, which is not something I would
say for columns.
--
Á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 | Greg Stark | 2011-06-22 23:37:24 | Re: Coding style point: "const" in function parameter declarations |
| Previous Message | Kevin Grittner | 2011-06-22 22:08:40 | Re: Repeated PredicateLockRelation calls during seqscan |