Re: tracking inherited columns (was: patch for check constraints using multiple inheritance) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)
Date
Msg-id 23993.1280948201@sss.pgh.pa.us
Whole thread Raw
In response to Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)  (Yeb Havinga <yebhavinga@gmail.com>)
Responses Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)  (Yeb Havinga <yebhavinga@gmail.com>)
List pgsql-hackers
Yeb Havinga <yebhavinga@gmail.com> writes:
> Tom Lane wrote:
>> I agree, this idea seems completely nuts.  It is *not* reasonable for
>> an action applied to a child to change the definition of the parent.

> Also not in the case that we're talking about here?

> A.a_column    B.a_column
>      |       /
>      v      v
>     C.a_column

> C inherits from A and B.

> The user wants to change a_column to better_name.

Well, if A and B inherited the column from a common ancestor, he can
easily do that.  If not, maybe he should have thought harder before he
started.  I do NOT agree that issuing a rename against C is a sane way
of dealing with this.

> This doesn't seem nuts to me.

You're in the minority.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rewrite, normal execution vs. EXPLAIN ANALYZE
Next
From: "Kevin Grittner"
Date:
Subject: Re: patch for contrib/isn