postgres cascade weird behaviour

From: Irwan Hendra <overtaker(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: postgres cascade weird behaviour
Date: 2009-04-17 01:50:46
Message-ID: 1b75c9a80904161850p3a16a062ifd96cb73ffe9ab06@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi

I have table A with pk that is being referenced by 5 other tables as foreign
key
I have put all those tables reference to be ON DELETE CASCADE
However for some reason when I tried to delete one of the row in table A,
out of 5 tables, 1 of them didn't actually get deleted
but the transaction is completed successfully
so I ended up with a table that has a foreign key referenced to a row that
doesn't exist anymore in table A

postgres is not reporting any error message, so I have no idea how to supply
more information to this problem

any idea?

Thanks

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2009-04-17 03:20:40 Re: Does anyone use postgreSQL(windows version)+Hibernate with middlegen?
Previous Message Rick Schumeyer 2009-04-17 01:43:13 Full text search strategy for names