From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Erik Thiele <erik(at)thiele-hydraulik(dot)de> |
Cc: | pgsql-sql(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [SQL] special integrity constraints |
Date: | 2004-03-23 00:34:56 |
Message-ID: | 20040323003456.GA7733@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-sql |
On Mon, Mar 22, 2004 at 17:21:21 +0100,
Erik Thiele <erik(at)thiele-hydraulik(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleus Mantzios | 2004-03-23 07:26:29 | Re: special integrity constraints |
Previous Message | Stephan Szabo | 2004-03-22 16:34:54 | Re: special integrity constraints |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory S. Williamson | 2004-03-23 02:16:19 | function definition documentation |
Previous Message | Stephan Szabo | 2004-03-22 16:34:54 | Re: special integrity constraints |