| From: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(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-23 18:44:57 |
| Message-ID: | BANLkTinzdt5usf85-dDU8uPdCOjzcmVdiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 22, 2011 at 3:37 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>wrote:
> Per:
>
> http://archives.postgresql.**org/pgsql-hackers/2010-11/**msg02043.php<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?
>
Instead of just synonyms of columns, why don't we think about implementing
virtual columns (feature as named in other RDBMS). This is the ability to
define a column in a table which is derived using an expression around other
non-virtual columns. I agree it would be much more difficult and some may
even argue it is pointless in the presence of views and expression indexes,
but I leave that as an exercise for others.
Regards,
--
Gurjeet Singh
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-06-23 18:58:54 | Re: SYNONYMS (again) |
| Previous Message | Florian Pflug | 2011-06-23 18:34:55 | Re: spinlock contention |