MIME-Version: 1.0
In-Reply-To: 
 <CAB8KJ=infML6Ac9VAt_FjOvsN5hv=ZW+gGC7kR-XsMfzPvi=sQ@mail.gmail.com>
References: 
 <CAB8KJ=infML6Ac9VAt_FjOvsN5hv=ZW+gGC7kR-XsMfzPvi=sQ@mail.gmail.com>
Date: Fri, 8 Mar 2013 15:33:39 -0500
Message-ID: 
 <CA+TgmoatmtvFtHmmDuGkDjNJfRfb0=5hNAFTPp5kw5e66LPy9A@mail.gmail.com>
Subject: Re: Small patch for "CREATE TRIGGER" documentation
From: Robert Haas <robertmhaas@gmail.com>
To: Ian Lawrence Barwick <barwick@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Wed, Mar 6, 2013 at 7:27 PM, Ian Lawrence Barwick <barwick@gmail.com> wrote:
> I found this sentence somewhat confusing:
>
> "It is possible for a column's value to change even when the trigger
> is not fired,"
>
> http://www.postgresql.org/docs/devel/static/sql-createtrigger.html#SQL-CREATETRIGGER-NOTES
>
> More precise would be something along the lines "It is possible that
> changes to the
> column's value will not cause the trigger to be fired".
>
> The attached patch hopefully rewords the entire paragraph for clarity.

I guess I prefer the current version, personally.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs