From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] Inherited Constraints |
Date: | 2006-03-06 21:53:17 |
Message-ID: | 1141681997.3810.4.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Ü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
---------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-03-06 22:25:16 | Re: [PATCHES] Inherited Constraints |
Previous Message | Bruno Wolff III | 2006-03-06 21:04:48 | Re: [PATCHES] LDAP auth |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-03-06 22:25:16 | Re: [PATCHES] Inherited Constraints |
Previous Message | Bruce Momjian | 2006-03-06 19:49:11 | Re: [HACKERS] Backslashes in string literals |