| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Cedar Cox <cedarc(at)visionforisrael(dot)com> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: triggered data change violation |
| Date: | 2001-03-20 18:13:53 |
| Message-ID: | 11744.985112033@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Cedar Cox <cedarc(at)visionforisrael(dot)com> writes:
> ERROR: triggered data change violation on relation "tblstsc2options"
> What is this? It doesn't happen unless I'm in a transaction. I'm
> INSERTing a record and then DELETEing it (in the same transaction) and on
> delete I get this error.
That's exactly what it's unhappy about ... but I'm not too clear on
just *why* that should be considered an uncool thing to do when you
have an AFTER trigger on the table. You're asking in the wrong list
though; try pgsql-hackers or pgsql-sql to see if someone knows why
this is bad.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cedar Cox | 2001-03-20 18:43:59 | triggered data change violation |
| Previous Message | Barry Lind | 2001-03-20 17:57:01 | Re: [INTERFACES] Trouble with JDBC2 ResultSet.getDate() |