Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)
Дата
Msg-id 23993.1280948201@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)  (Yeb Havinga <yebhavinga@gmail.com>)
Ответы Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)  (Yeb Havinga <yebhavinga@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Rewrite, normal execution vs. EXPLAIN ANALYZE
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: patch for contrib/isn