| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Cc: | "Glenn MacGregor" <gtm(at)oracom(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Transaction and cascade problem |
| Date: | 2001-12-20 17:09:11 |
| Message-ID: | 9261.1008868151@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Josh Berkus" <josh(at)agliodbs(dot)com> writes:
>> ERROR: triggered data change violation on relation "groups"
> Yes. For some technical reason ( I'm not clear on this ) you cannot
> both add and delete the same row within a PostgreSQL transaction. This
> is a known issue in 7.1.x; I do not know if it is fixed in 7.2.
Actually, we've just removed that error check in 7.2. The discussion
concluded that we'd misinterpreted the spec in treating this condition
as an error. You can simply dike out the error call (it's in
src/backend/commands/trigger.c, IIRC) if it's getting in your way in
7.1.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter T. Brown | 2001-12-20 17:27:08 | Re: controlling process priority |
| Previous Message | Josh Berkus | 2001-12-20 16:08:14 | Re: Transaction and cascade problem |