This was a mistake in the interpretation of the spec (modification of the same key row referenced by a foreign key constraint in the same statement more than once is an error is how we believe the spec meant it, but there's a case where they mention transaction and it got misinterpreted). I don't think anyone's permanently fixed it yet, but making the check disappear involves commenting out the two blocks that throw the message in backend/commands/trigger.c. On Wed, 29 Aug 2001, Pawel Pawlowski wrote: > Im changing now database from Interbase 6.0 to PosgreSql 7.1.2. With IB > there is no problem to do such things. > This problem only exist when I create table tbl_a with references > (REFERENCES tbl_a (pn_id) ON UPDATE CASCADE ON DELETE CASCADE). Without this > part everything works OK. So I think that problem is with triger. ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
