Обсуждение: postgres cascade weird behaviour
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
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
On Thursday 16 April 2009 6:50:46 pm Irwan Hendra wrote: > 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 Turn up the logging in postgresql.conf -- Adrian Klaver aklaver@comcast.net