Re: concurent updates - Mailing list pgsql-general

From Stephan Szabo
Subject Re: concurent updates
Date
Msg-id Pine.BSF.4.21.0107261059400.77564-100000@megazone23.bigpanda.com
Whole thread Raw
In response to concurent updates  ("Steve SAUTETNER" <ssa@informactis.com>)
Responses What's going on here?  ("Dave Cramer" <Dave@micro-automation.net>)
List pgsql-general
On Thu, 26 Jul 2001, Steve SAUTETNER wrote:

> hi everybody !
>
> I've got a little problem when updating a primary key in two table
> where the primary key of the one is a foreign key from the second :
>
> here are the 2 tables :
>
> create table table1 (id int primary key, col1 int);
> create table table2 (id int primary key references table1(id), col2 int);
>
> and the 2 updates :
>
> 1) update table2 set id = 1001 where id = 1;
> 2) update table1 set id = 1001 where id = 1;
>
> i can't execute them separately because of an integrity constraint
> violation.
> i've got the same error in a BEGIN / COMMIT block containing the updates.
>
> Does any one see how two help me ?

Either on update cascade (as suggested by someone else) or making the
constraint deferred in which case you can use a begin...commit block.


pgsql-general by date:

Previous
From: Barry Lind
Date:
Subject: Re: [SQL] When PostgreSQL compliant JDBC 2.0? (Batch updates)
Next
From: "Dave Cramer"
Date:
Subject: What's going on here?