Hi,
...
> key reference). Isn't then the query valid for those tuples which do not
> result in a violation of the referential integrity test? Shouldn't those
> tuples in a be deleted?
The "all or nothing" approach causes this. And _here_ **I think** its
correct behaviour. (IMHO user and backend
Title: RE: [HACKERS] Foreign key checks/referential integrity.
No, they shouldn't. If you want to delete only those tuples that aren't referenced in b then you must explicitly say so:
delete from a where not exists (select * from b where b.b = a.a);
The query that you
Hi guys,
I've just come up with a hypothetical which, in my opinion, points to a
flaw in the foreign key implementation in Postgres. All tests were
conducted on 7.1beta4 -- not the most up to date, but I have seen no
reference to this in the mailing list/todo (ie, in 'foreign' under
TODO.detail).
