| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Yeb Havinga <yebhavinga(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Henk Enting <h(dot)d(dot)enting(at)mgrid(dot)net>, pgsql-hackers(at)postgresql(dot)org, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Subject: | Re: tracking inherited columns (was: patch for check constraints using multiple inheritance) |
| Date: | 2010-08-04 12:56:17 |
| Message-ID: | 4C596371.1000204@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/04/2010 06:41 AM, Robert Haas wrote:
> On Wed, Aug 4, 2010 at 6:41 AM, Yeb Havinga<yebhavinga(at)gmail(dot)com> wrote:
>>> If child inherits column A from parent1 and parent2, and it is then
>>> renamed to B in parent2, what should the name be in the child after
>>> the rename is completed?
>> The column should be renamed to B in parent2, child and parent1.
> Uh, really? Wow. You want to follow the inheritance hierarchy in
> both directions, both down and up? That seems like it could be
> confusing.
>
>
It seems more than confusing. It seems fundamentally wrong. It would
certainly be a violation of POLA.
Unless there's an extremely persuasive case made for it I'm inclined
just to say no.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-08-04 13:00:19 | Re: Review of Synchronous Replication patches |
| Previous Message | Robert Haas | 2010-08-04 12:53:15 | Re: review: psql: edit function, show function commands patch |