From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Erik Thiele <erik(at)thiele-hydraulik(dot)de> |
Cc: | Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: special integrity constraints |
Date: | 2004-03-22 14:21:28 |
Message-ID: | 20040322061854.W56073@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-sql |
On Mon, 22 Mar 2004, Erik Thiele wrote:
> 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....
However, foreign keys are implemented using "constraint triggers". They're
really not documented much (because they're a not really separately
supported implementation detail), but you can theoretically make
triggers that are deferred to immediately before commit time.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2004-03-22 15:12:11 | Re: special integrity constraints |
Previous Message | Erik Thiele | 2004-03-22 13:10:42 | Re: special integrity constraints |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2004-03-22 15:12:11 | Re: special integrity constraints |
Previous Message | Martin Marques | 2004-03-22 13:14:40 | Re: inverse of "day of year" |