| From: | Trent Shipley <tshipley(at)deru(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] Inherited Constraints |
| Date: | 2005-12-09 01:29:01 |
| Message-ID: | 200512081829.02377.tshipley@deru.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Thursday 2005-12-08 15:47, Simon Riggs wrote:
> does of course already exist, so the following should cause dependency
> violation ERRORs:
> - omitting the CASCADE when attempting to delete parent constraint
> - attempting to drop the child constraint
Why should dropping the child constraint fail?
Child tables are supposed to be able to over-ride parent constraints.
Dropping a parent's constraint sounds like just a way to over-ride a
constraint with no constraint at all. (Making the column unconstrained.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-12-09 01:43:05 | Re: [PATCHES] Inherited Constraints |
| Previous Message | Tom Lane | 2005-12-09 01:26:45 | Re: generic builtin functions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-12-09 01:37:19 | initdb detecting date order |
| Previous Message | Simon Riggs | 2005-12-08 22:47:08 | Re: [PATCHES] Inherited Constraints |