Re: Odp: PD: triggered data change violation on relation "tbl_b"
От | Stephan Szabo |
---|---|
Тема | Re: Odp: PD: triggered data change violation on relation "tbl_b" |
Дата | |
Msg-id | Pine.BSF.4.21.0108291125110.48187-100000@megazone23.bigpanda.com обсуждение исходный текст |
Ответ на | Odp: PD: triggered data change violation on relation "tbl_b" ("Pawel Pawlowski" <pawel.pawlowski@breitenbach.pl>) |
Ответы |
Re: Odp: PD: triggered data change violation on relation "tbl_b"
|
Список | pgsql-bugs |
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.
В списке pgsql-bugs по дате отправления: