From: Bruno Wolff III <bruno@wolff.to>
To: Erik Thiele <erik@thiele-hydraulik.de>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-docs@postgresql.org
Subject: Re: [SQL] special integrity constraints
Date: Mon, 22 Mar 2004 18:34:56 -0600
Message-ID: <20040323003456.GA7733@wolff.to> (raw)
In-Reply-To: <20040322172121.72ecf58b.erik@thiele-hydraulik.de>
References: <20040322102031.6a6f0b77.erik@thiele-hydraulik.de>
<20040322112604.GA31222@wolff.to>
<20040322141042.0aeb936d.erik@thiele-hydraulik.de>
<20040322151211.GA2962@wolff.to>
<20040322172121.72ecf58b.erik@thiele-hydraulik.de>
On Mon, Mar 22, 2004 at 17:21:21 +0100,
Erik Thiele <erik@thiele-hydraulik.de> wrote:
>
> there is no such thing as a deferred check 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. !!!
Sorry, I checked the syntax for CREATE TABLE in the documentation and
it shows DEFERRABLE as allowed on any column constraint. However, that
is apparently not correct.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bruno@wolff.to, erik@thiele-hydraulik.de, pgsql-docs@postgresql.org
Subject: Re: [SQL] special integrity constraints
In-Reply-To: <20040323003456.GA7733@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox