From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Resp.: Problem defining deferred check constraints |
Date: | 2009-01-25 16:10:15 |
Message-ID: | gli2t5$230$1@ger.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Osvaldo Kussama wrote on 25.01.2009 15:24:
> See the manual:
> http://www.postgresql.org/docs/current/interactive/sql-createtable.html
> "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 can 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.*"
>
Thanks for reading the manual for me :)
Maybe the syntax definition for the /column_constraint/ part should be reworked
to make that clearer, by e.g. putting the DEFERRED stuff in to the "choice" for
FK definitions not at the end where it is "legal" for any constraint.
Regards
Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Roger Leigh | 2009-01-25 17:07:56 | Re: Custom type, operators and operator class not sorting/indexing correctly |
Previous Message | Martijn van Oosterhout | 2009-01-25 16:08:54 | Re: Custom type, operators and operator class not sorting/indexing correctly |