| From: | PostgreSQL - Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Joshua D(dot) Drake <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SYNONYMS (again) |
| Date: | 2011-06-23 07:03:31 |
| Message-ID: | 99AFF93E-C607-41B5-A343-A3EFF97D1CFB@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
yes, implementing synonyms is not too hard.
some time ago (3 or 4 years ago most likely) we already posted a patch providing support for synonyms.
it was rejected because synonyms were said to be a bad design pattern which app developers to do nasty things.
so, if you want to work on it maybe this patch is the place to start.
many thanks,
hans
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL - Hans-Jürgen Schönig | 2011-06-23 07:04:17 | Re: SYNONYMS (again) |
| Previous Message | Jun Ishiduka | 2011-06-23 06:41:09 | Re: Online base backup from the hot-standby |