| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Jan Wieck <janwieck(at)Yahoo(dot)com>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Questions on RI spec (poss. bugs) |
| Date: | 2000-11-22 16:16:06 |
| Message-ID: | 3A1BF146.7552AEE6@tm.ee |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>
> Jan Wieck writes:
>
> > Stephan Szabo wrote:
> > >
> > > There's a message on -general about a possible
> > > problem in the deferred RI constraints. He was doing a
> > > sequence like:
> > > begin
> > > delete
> > > insert
> > > end
> > > and having it fail even though the deleted key was back in
> > > place at the end.
> >
> > Isn't that (delete and reinsert the same PK) what the
> > standard means with "triggered data change violation"?
>
> Triggered data change violations can only occur if the same attribute is
> changed twice during the same *statement*, not transaction.
>
Do we also get "Triggered data change violations" when we delete and
then
insert on the FK side in a single transaction ?
I just had to remove a FK constraint because I could not figure ot where
the violation was coming from ;(
-----------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-11-22 16:34:02 | Re: pg_dump / Unique constraints |
| Previous Message | Tom Lane | 2000-11-22 16:15:59 | Re: pg_dump / Unique constraints |