| 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:41:18 |
| Message-ID: | AANLkTimjNzpW7Z6QGDOTMQKJO8cTC-s_jHhGBBjCb5z0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 4, 2010 at 6:41 AM, Yeb Havinga <yebhavinga(at)gmail(dot)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.
>> 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?
>
> If the change happens in a single transaction there should be no problems
> here, as opposed to e.g. have the user issue two renames. Did I get the
> bonus points? :-)
Sure, though I'm not sure I like the basic idea. :-)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yeb Havinga | 2010-08-04 10:41:24 | Re: tracking inherited columns (was: patch for check constraints using multiple inheritance) |
| Previous Message | Robert Haas | 2010-08-04 10:34:25 | Re: tracking inherited columns (was: patch for check constraints using multiple inheritance) |