From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Pawel Pawlowski <pawel(dot)pawlowski(at)breitenbach(dot)pl> |
Cc: | pgsql-bugs(at)postgresql(dot)org, Andreas Wernitznig <andreas(at)insilico(dot)com> |
Subject: | Re: Odp: PD: triggered data change violation on relation "tbl_b" |
Date: | 2001-08-29 18:27:52 |
Message-ID: | Pine.BSF.4.21.0108291125110.48187-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-08-29 18:30:24 | Re: Indices get ignored in large tables |
Previous Message | Pawel Pawlowski | 2001-08-29 11:43:15 | Odp: PD: triggered data change violation on relation "tbl_b" |