pgsql: doc: clearify trigger behavior for inheritance
doc: clearify trigger behavior for inheritance
The previous wording added in PG 10 wasn't specific enough about the
behavior of statement and row triggers when using inheritance.
Reported-by: ian@thepathcentral.com
Discussion: /messages/by-id/20171129193934.27108.30796@wrigleys.postgresql.org
Backpatch-through: 10
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/1cf1112990cff432b53a74a0ac9ca897ce8a7688
Modified Files
--------------
doc/src/sgml/ref/create_trigger.sgml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
On Wed, Jan 31, 2018 at 5:00 PM, Bruce Momjian <bruce@momjian.us> wrote:
doc: clearify trigger behavior for inheritance
The previous wording added in PG 10 wasn't specific enough about the
behavior of statement and row triggers when using inheritance.
This may be a good change in general, but the change of "affected" to
"effected" is bad English.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Wed, Jan 31, 2018 at 05:13:41PM -0500, Robert Haas wrote:
On Wed, Jan 31, 2018 at 5:00 PM, Bruce Momjian <bruce@momjian.us> wrote:
doc: clarify trigger behavior for inheritance
The previous wording added in PG 10 wasn't specific enough about the
behavior of statement and row triggers when using inheritance.This may be a good change in general, but the change of "affected" to
"effected" is bad English.
Thanks, fixed. I struggled with that word.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +