Re: SYNONYMS (again) - Mailing list pgsql-hackers

From PostgreSQL - Hans-Jürgen Schönig
Subject Re: SYNONYMS (again)
Date
Msg-id 23A65C90-7AE7-42AE-A973-3439498DC6E6@cybertec.at
Whole thread Raw
In response to Re: SYNONYMS (again)  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Jun 23, 2011, at 12:52 AM, Alvaro Herrera wrote:

> 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.



sorry, i missed the links:

http://archives.postgresql.org/pgsql-patches/2006-03/msg00085.php
many thanks,
    hans


--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de



pgsql-hackers by date:

Previous
From: PostgreSQL - Hans-Jürgen Schönig
Date:
Subject: Re: SYNONYMS (again)
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Hugetables question