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

Поиск
Список
Период
Сортировка
От Yeb Havinga
Тема Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)
Дата
Msg-id 4C594703.20103@gmail.com
обсуждение исходный текст
Ответ на Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas wrote:
> On Wed, Aug 4, 2010 at 6:41 AM, Yeb Havinga <yebhavinga@gmail.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.
>   
Yes, the idea is to follow the up direction in the case of column 
changes, only if the column is already present in another parent. To 
avoid confusion we could block the first attempt of a change with a 
message other parents exists, and the hint to add e.g. CASCADE to update 
the definition in the other parent as well.

-- Yeb



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)
Следующее
От: Alexander Korotkov
Дата:
Сообщение: Re: multibyte charater set in levenshtein function