Skip site navigation (1) Skip section navigation (2)

Re: Referential integrity problem

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: d(dot)sbragion(at)infotecna(dot)it, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Referential integrity problem
Date: 2001-06-18 18:03:32
Message-ID: Pine.BSF.4.21.0106181100540.85469-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Mon, 18 Jun 2001 pgsql-bugs(at)postgresql(dot)org wrote:

> Denis Sbragion (d(dot)sbragion(at)infotecna(dot)it) reports a bug with a severity of 3
> The lower the number the more severe it is.
> 
> Short Description
> Referential integrity problem
> 
> Long Description It looks like performing operation in two steps on
> tables with multiple deferred referential integrity constraints
> between them is not allowed. Not sure this is a bug, may be it is
> required by the standards, but sure it is rater counterintuitive (may
> be, of course, I'm completely wrong). Most of the times this is just
> annoying, sometimes it doesn't let you do updates, i.e. whenever you
> cannot perform the update in a single step (I found at least one
> case). Tested both on 7.0.3 and 7.1.2, with same results.
> 
> P.S. Great job guys. 7.0.3 was very good, but 7.1.2 is simply wonderful.

Yep.  AFAICT it's currently broken for such cases.  I've been working
(slowly :() on fixing it so it doesn't try the checks on rows that are no
longer valid (such as the intermediate states of multiple updates).



In response to

pgsql-bugs by date

Next:From: Piotr KrukowieckiDate: 2001-06-18 19:59:35
Subject: psql (frontend) segfaults
Previous:From: Patti MorganDate: 2001-06-18 17:26:12
Subject: RE: Referential integrity problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group