From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrzej Mazurkiewicz <andrzej@mazurkiewicz.org>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Inheritance of foregn key constraints.
Date: Fri, 21 Mar 2014 10:14:03 -0400
Message-ID: <15558.1395411243@sss.pgh.pa.us> (raw)
In-Reply-To: <1523734.6NloWteI3S@tata>
References: <1523734.6NloWteI3S@tata>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Andrzej Mazurkiewicz <andrzej@mazurkiewicz.org> writes:
> My patch need one change that might be of significance.
> A type of the depencencies (pg_depend) among the FK constraint (pg_constraint)
> and the corresponding "RI_ConstraintTrigger" triggers has to be changed from
> DEPENDENCY_INTERNAL to DEPENDENCY_AUTO.
So in other words, somebody could (accidentally or maliciously) break the
constraint by dropping one of its implementation triggers. I doubt that's
acceptable.
> If this modification is not applied, the detail child table cannot be dropped
> without prevous dropping the whole FK constraint because the removing
> operation depend on the FK constraint of its parent table.
Dropping a child table is going to have much larger problems than that,
no? What about the values in the child table --- don't you risk orphaning
referencing rows? Or are you only supporting this on the referencing
side?
In any case, it seems like DROP TABLE could remove the dependency entries
for itself, rather than taking the risk of weakening the dependency type.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrzej@mazurkiewicz.org
Subject: Re: Inheritance of foregn key constraints.
In-Reply-To: <15558.1395411243@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox