| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Yeb Havinga <yebhavinga(at)gmail(dot)com> |
| Cc: | 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 10:34:25 |
| Message-ID: | AANLkTikXjOQdmVAtz6GaaJmj66f7pz8C49ZAE=iVWgPm@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 4, 2010 at 3:48 AM, Yeb Havinga <yebhavinga(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-08-04 10:41:18 | Re: tracking inherited columns (was: patch for check constraints using multiple inheritance) |
| Previous Message | Robert Haas | 2010-08-04 10:32:11 | Re: documentation for committing with git |