From: | PFC <lists(at)peufeu(dot)com> |
---|---|
To: | "Ron Johnson" <ron(dot)l(dot)johnson(at)cox(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pointer to feature comparisons, please |
Date: | 2007-06-14 07:24:54 |
Message-ID: | op.ttwhjth2cigqcu@apollo13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>>> The DELETE should block, no?
>> Why ?
>> Foreign keys put an ON DELETE trigger on the referenced table
>
> Foreign keys that silently, automatic DELETE records?
> Did I read that correctly?
Isn't that the point of ON DELETE CASCADE ?
>> besides checking the referencing column on insert/update... If you just
>> implement a constraint, you only get half the functionality.
>
> But when I define a FK *constraint*, that's all I *want*!
When you add a REFERENCE foo( bar ) foreign key and don't specify ON
DELETE clause, I believe you get ON DELETE NO ACTION, which means the
referenced row can't be deleted if there are referencing rows... so when
you have a FK constraint, it actually constrains two tables, and pg uses
share locking to ensure race conditions can't cause an inconsistent
database.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2007-06-14 07:39:31 | Re: function to find difference between in days between two dates |
Previous Message | Manso Gomez, Ramon | 2007-06-14 07:03:48 | Re: [SQL] setof or array as input parameter to postgresql 8.2 functions |