| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
| Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Small patch for "CREATE TRIGGER" documentation |
| Date: | 2013-03-08 20:33:39 |
| Message-ID: | CA+TgmoatmtvFtHmmDuGkDjNJfRfb0=5hNAFTPp5kw5e66LPy9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Wed, Mar 6, 2013 at 7:27 PM, Ian Lawrence Barwick <barwick(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-03-10 21:17:51 | Re: The relation between "checkpoint_timeout" and "checkpoint_warning" is missing |
| Previous Message | Bruce Momjian | 2013-03-08 17:20:13 | Re: [HACKERS] Contrib module "xml2" status |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-03-08 20:39:06 | Re: Duplicate JSON Object Keys |
| Previous Message | Dann Corbit | 2013-03-08 20:11:29 | Re: Why do we still perform a check for pre-sorted input within qsort variants? |