Re: Many-to-many with both FK cascading deletes?
Date: Sun, 20 Jun 2010 16:14:46 -0700 (PDT)
Message-ID: <1899e132-864c-41ac-a218-5ba1fd90e5f2_at_h13g2000yqm.googlegroups.com>
On 19 jun, 22:04, Karsten Wutzke <kwut..._at_web.de> wrote:
> Hello,
>
> are there any complications in general with a many-to-many "join
> table" having cascading deletes on both foreign keys to the
> interconnected tables? After all, this means that the "link entities"
> get deleted whoever comes first... could this pose a problem?
>
> I cannot think of any concrete examples where this could really do
> harm, but if there are, please enlighten me.
>
> Karsten
Sorry, fail to see how this has anything to do with database theory.
The concept of "cascade delete" is pretty well understood and pretty well-defined, and if some DBMS chooses to support it, it is that DBMS's responsibility to do so properly. That is, it is the responsibility of that DBMS's authors to see to it that their implementation does not cause any "problems". If it did, their implementation would be flawed. Received on Mon Jun 21 2010 - 01:14:46 CEST