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 <alvhe...@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to