From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Hannu Krosing <hannu(at)skype(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Bizgres-general] A Guide to Constraint Exclusion |
Date: | 2005-07-15 12:35:33 |
Message-ID: | 1121430933.3970.520.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2005-07-15 at 11:10 +0300, Hannu Krosing wrote:
> Bruce: could you change this TODO item
>
> o Prevent child tables from altering constraints like CHECK that were
> inherited from the parent table
>
> to
>
> o Prevent new child tables from inheriting constraints defined on
> parents with keyword ONLY:
> alter table ONLY t add constraint c check(x=y);
> Prevent child tables from altering constraints that were
> inherited from the parent table (i.e were defined without
> ONLY/with ALL)
My thought was to introduce a new type of constraint, ABSTRACT.
This would not be inherited (it is not a check constraint). It would
allow a table to be declared "will never contain rows".
This fits better with the ideas and common understandings of
inheritance.
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-07-15 14:07:37 | Re: pg_get_prepared? |
Previous Message | Hannu Krosing | 2005-07-15 08:10:34 | Re: [Bizgres-general] A Guide to Constraint Exclusion |