Skip site navigation (1) Skip section navigation (2)

Re: Constraint trigger doc patch

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Michael Paesold <mpaesold(at)gmx(dot)at>
Cc: Michael Glaesemann <grzm(at)myrealbox(dot)com>, pgsql-patches Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Constraint trigger doc patch
Date: 2006-10-17 12:53:04
Message-ID: 200610171253.k9HCr4913613@momjian.us (view raw or flat)
Thread:
Lists: pgsql-patches
Patch applied.  Thanks.  Your documentation changes can be viewed in
five minutes using links on the developer's page,
http://www.postgresql.org/developer/testing.


---------------------------------------------------------------------------


Michael Paesold wrote:
> Bruce Momjian schrieb:
> > Manual page changed applied.  Thanks.
> 
> Ok, here is small patch fixing the remaining items I found when 
> reviewing the built page. Two items are just SGML bugs, the other item 
> is to finish an incomplete change from the previous "events" to the new 
> "event [ OR ... ]" notation.
> 
> Best Regards,
> Michael Paesold
> 
> For quick reference:
> http://momjian.us/main/writings/pgsql/sgml/sql-createconstraint.html

> Index: create_constraint.sgml
> ===================================================================
> RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v
> retrieving revision 1.16
> diff -c -r1.16 create_constraint.sgml
> *** doc/src/sgml/ref/create_constraint.sgml	16 Oct 2006 19:33:12 -0000	1.16
> --- doc/src/sgml/ref/create_constraint.sgml	17 Oct 2006 06:48:14 -0000
> ***************
> *** 52,58 ****
>        <para>
>         The name of the constraint trigger. The actual name of the
>         created trigger will be of the form
> !       <literal>RI_ConstraintTrigger_0000<literal> (where 0000 is some number
>         assigned by the server).
>         Use this assigned name when dropping the trigger.
>        </para>
> --- 52,58 ----
>        <para>
>         The name of the constraint trigger. The actual name of the
>         created trigger will be of the form
> !       <literal>RI_ConstraintTrigger_0000</literal> (where 0000 is some number
>         assigned by the server).
>         Use this assigned name when dropping the trigger.
>        </para>
> ***************
> *** 60,71 ****
>      </varlistentry>
>   
>      <varlistentry>
> !     <term><replaceable class="PARAMETER">events</replaceable></term>
>       <listitem>
>        <para>
>         One of <literal>INSERT</literal>, <literal>UPDATE</literal>, or
>         <literal>DELETE</literal>; this specifies the event that will fire the
> !       trigger. Multiple events can be specified using <literal>OR<literal>.
>        </para>
>       </listitem>
>      </varlistentry>
> --- 60,71 ----
>      </varlistentry>
>   
>      <varlistentry>
> !     <term><replaceable class="PARAMETER">event</replaceable></term>
>       <listitem>
>        <para>
>         One of <literal>INSERT</literal>, <literal>UPDATE</literal>, or
>         <literal>DELETE</literal>; this specifies the event that will fire the
> !       trigger. Multiple events can be specified using <literal>OR</literal>.
>        </para>
>       </listitem>
>      </varlistentry>

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings

-- 
  Bruce Momjian   bruce(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-patches by date

Next:From: Toru SHIMOGAKIDate: 2006-10-18 00:35:39
Subject: BUG #2704: pg_class.relchecks overflow problem
Previous:From: Michael GlaesemannDate: 2006-10-17 09:17:25
Subject: Re: Constraint trigger doc patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group