Re: Improving CREATE CONSTRAINT TRIGGER documentation - trigger firing order - Mailing list pgsql-docs

From Michael Glaesemann
Subject Re: Improving CREATE CONSTRAINT TRIGGER documentation - trigger firing order
Date
Msg-id EA1B473D-1D3E-432A-9E02-DA96621C965A@seespotcode.net
Whole thread Raw
In response to Improving CREATE CONSTRAINT TRIGGER documentation - trigger firing order  (David Pufer <david.pufer@7data.eu>)
Responses Re: Improving CREATE CONSTRAINT TRIGGER documentation - trigger firing order  (David Pufer <david.pufer@7data.eu>)
Re: Improving CREATE CONSTRAINT TRIGGER documentation - trigger firing order  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On Apr 21, 2007, at 4:39 , David Pufer wrote:

> In my opinion it would be nice to mention in SQL reference commands
> that
> constraint triggers created by CREATE CONSTRAINT TRIGGER are fired in
> creation order unlike regular triggers created by command CREATE
> TRIGGER. As I know, the firing order of the CONSTRAINT TRIGGER is
> determined by the XXXXX num at "RI_ConstraintTrigger_XXXXX" column in
> pg_trigger table.

I believe this just falls out of the normal order of trigger firing
as explained in the CREATE TRIGGER documentation (http://
www.postgresql.org/docs/8.2/interactive/sql-createtrigger.html)

> If multiple triggers of the same kind are defined for the same
> event, they will be fired in alphabetical order by name.

It might be nice to add a similar phrase to the CREATE CONSTRAINT
TRIGGER documentation, but as far as I know, the behavior is the same
for triggers created by either method. The only difference is that
constraint triggers are named by the system rather than by the user.

Thoughts?

Michael Glaesemann
grzm seespotcode net



pgsql-docs by date:

Previous
From: David Pufer
Date:
Subject: Improving CREATE CONSTRAINT TRIGGER documentation - trigger firing order
Next
From: David Pufer
Date:
Subject: Re: Improving CREATE CONSTRAINT TRIGGER documentation - trigger firing order