From: wieck@debis.com
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: PostgreSQL-documentation <docs@postgresql.org>
Subject: Re: [HACKERS] TODO doc items
Date: Thu, 13 Apr 2000 09:33:46 +0200 (CEST)
Message-ID: <m12fe8I-0003knC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <200004130428.AAA06245@candle.pha.pa.us>
Bruce Momjian wrote:
> Here are the open doc items. Should we consider ecpg.sgml as up-to-date
> as it needs to be for 7.0? Can I get someone working on the other
> items, hopefully the authors?
>
> ---------------------------------------------------------------------------
>
> > New CREATE CONSTRAINT TRIGGER and SET CONSTRAINTS commands(Jan)
>
> No man page yet. Not sure what command SET CONSTRAINT applies to.
>
CREATE CONSTRAINT TRIGGER is used from inside of CREATE/ALTER
TABLE and by pg_dump to create the special triggers for
referential integrity. Dunno if we really need a manpage for
it.
SET CONSTRAINTS is the SQL3 specified command to change the
default behaviour of constraints WRT deferring in the current
transaction.
Syntax is:
SET CONSTRAINTS {ALL | <constraintlist>} <mode>
<constraintlist> := comma separated list of deferrable
constraint names
<mode> := DEFERRED | IMMEDIATE
In deferred mode, the actual check of the constraint is held
back until either it's mode is explicitly set to IMMEDIATE,
or until COMMIT. This is actually only done for foreign key
constraints, so it does not apply to UNIQUE or other
constraints.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck@debis.com (Jan Wieck) #
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-docs@postgresql.org
Cc: wieck@debis.com, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org, docs@postgresql.org
Subject: Re: [HACKERS] TODO doc items
In-Reply-To: <m12fe8I-0003knC@orion.SAPserv.Hamburg.dsh.de>
* 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