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

Re: special integrity constraints

From: Erik Thiele <erik(at)thiele-hydraulik(dot)de>
To: Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: special integrity constraints
Date: 2004-03-22 10:26:59
Message-ID: 20040322112659.4553df76.erik@thiele-hydraulik.de (view raw or flat)
Thread:
Lists: pgsql-docspgsql-sql
On Mon, 22 Mar 2004 12:13:29 +0200 (EET)
Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> wrote:

> O kyrios Erik Thiele egrapse stis Mar 22, 2004 :
> 
> Did you check out the DEFERRABLE option on the constraint?
> 

DEFERRABLE
NOT DEFERRABLE

This controls whether the constraint can be deferred. A constraint that
is not deferrable will be checked immediately after every command.
Checking of constraints that are deferrable may be postponed until the
end of the transaction (using the SET CONSTRAINTS command). NOT
DEFERRABLE is the default. 

!!!! Only foreign key constraints currently accept
this clause. All other constraint types are not deferrable. !!!!

my constraint is not a foreign key constraint....

cya!
erik

> > hi,
> > 
> > i have two tables
> > 
> > create table a (x integer);
> > create table b (y real);
> > 
> > i have the special constraint that the sum of the number of rows in
> > table a plus the number of rows in table b must be even.
> > 
> > so there is a posibility of adding one element to a and one element
> > to b, and again the constraint is met.
> > 
> > but this of course does not work, since between adding the element
> > to a and adding the element to b, the constraint is not met.
> > 
> > so i cannot use a trigger.
> > 
> > what i need is the execution of a check procedure at commit time. is
> > that somehow possible?
> > 
> > my database has much more tables than just a and b, and most time
> > the other tables are modified and not a or b, so it would be nice to
> > execute the constraint checking procedure only if a or b was
> > modified.
> > 
> > yes :) this question i asked in my former mail too, but I think it
> > looked like there was a workaround and my problem was wrong. so i
> > created this new kind of problem here to make things clearer.
> > 
> > 
> > cu
> > Erik
> > 
> > 
> > 
> 
> -- 
> -Achilleus
> 


-- 
Erik Thiele
Horst Thiele Maschinenbau-Hydraulische Geräte GmbH
Im Kampfrad 2 - 74196 Neuenstadt
Tel.: 07139/4801-19
Fax.: 07139/4801-29
email: erik(at)thiele-hydraulik(dot)de
Internet: http://www.thiele-hydraulik.de/

In response to

Responses

pgsql-docs by date

Next:From: Bruno Wolff IIIDate: 2004-03-22 11:26:04
Subject: Re: special integrity constraints
Previous:From: Achilleus MantziosDate: 2004-03-22 10:13:29
Subject: Re: special integrity constraints

pgsql-sql by date

Next:From: Bruno Wolff IIIDate: 2004-03-22 11:26:04
Subject: Re: special integrity constraints
Previous:From: Achilleus MantziosDate: 2004-03-22 10:13:29
Subject: Re: special integrity constraints

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