Re: tracking inherited columns (was: patch for check constraints using multiple inheritance)
| От | Robert Haas |
|---|---|
| Тема | Re: tracking inherited columns (was: patch for check constraints using multiple inheritance) |
| Дата | |
| Msg-id | AANLkTikXjOQdmVAtz6GaaJmj66f7pz8C49ZAE=iVWgPm@mail.gmail.com обсуждение исходный текст |
| Ответ на | 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)
|
| Список | pgsql-hackers |
On Wed, Aug 4, 2010 at 3:48 AM, Yeb Havinga <yebhavinga@gmail.com> wrote: > I just read that thread. In the beginning there is a short discussion what > the non-astonishing behaviour of the RENAME in the case of multiple origin > inheritance should be, which is preventing renames or any property change in > that case. I think we should explore the possibilty of allowing the RENAME > more. 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? For bonus points, how should pg_dump handle this to make sure the state after a dump and reload matches the state before the dump and reload? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: