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

Re: SYNONYMS (again)

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Excerpts from Joshua D. Drake's message of mié jun 22 15:37:17 -0400 2011:
> Per:
> 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

In response to


pgsql-hackers by date

Next:From: Greg StarkDate: 2011-06-22 23:37:24
Subject: Re: Coding style point: "const" in function parameter declarations
Previous:From: Kevin GrittnerDate: 2011-06-22 22:08:40
Subject: Re: Repeated PredicateLockRelation calls during seqscan

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