From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hannu Krosing <hannu(at)skype(dot)net> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] Inherited Constraints |
Date: | 2006-03-06 22:25:16 |
Message-ID: | 200603062225.k26MPGI21439@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Hannu Krosing wrote:
> ?hel kenal p?eval, E, 2006-03-06 kell 12:12, kirjutas Bruce Momjian:
> > Added to TODO:
> >
> > o Prevent parent tables from altering or dropping constraints
> > like CHECK that are inherited by child tables
> >
> > Dropping constraints should only be possible with CASCADE.
> >
> > and we already have this in TODO:
> >
> > o %Prevent child tables from altering or dropping constraints
> > like CHECK that were inherited from the parent table
> >
> > so I think we now have all the failure cases documented.
>
> If you want to be consistent, then ALTER TABLE ONLY ADD CONSTRAINT ..
> should also be forbidden, so you can't create non-inherited constraints
I don't have a problem with creating ONLY constraints on parents and
children. We just don't want them to be removed/modified if they are
shared.
--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-03-06 22:57:04 | SQL string warning |
Previous Message | Hannu Krosing | 2006-03-06 21:53:17 | Re: [PATCHES] Inherited Constraints |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-07 01:38:58 | Re: [HACKERS] Zeroing damaged pages |
Previous Message | Hannu Krosing | 2006-03-06 21:53:17 | Re: [PATCHES] Inherited Constraints |