Re: [HACKERS] TODO doc items
От | wieck@debis.com (Jan Wieck) |
---|---|
Тема | Re: [HACKERS] TODO doc items |
Дата | |
Msg-id | m12fe8I-0003knC@orion.SAPserv.Hamburg.dsh.de обсуждение исходный текст |
Ответ на | TODO doc items (Bruce Momjian <pgman@candle.pha.pa.us>) |
Список | pgsql-docs |
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) #
В списке pgsql-docs по дате отправления: