From: | <cnliou(at)eurosport(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | What Is The Firing Order? |
Date: | 2001-09-07 08:24:09 |
Message-ID: | 200109070824.098a@lh00.opsion.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings!
The document says: "Also, if more than one trigger is
defined for the same event on the same relation, the
order of trigger firing is unpredictable. This may be
changed in the future."
My another question is: When both UPDATE trigger (and
its trigger function) and UPDATE CASCADE constraint
are both defined, is the custom UPDATE trigger or the
UPDATE CASCADE constraint fired first?
I wish the constraint will be fired first. Otherwise,
I should not define the constraint (which saves a lot
of work) and code the complex UPDATE CASCADE actions
in the trigger to replace the powerful constraint
functionality during table creation, in order to see
data changed in the expected order. Am I correct?
Thanks!
CN
--------------------------------------------------------
You too can have your own email address from Eurosport.
http://www.eurosport.com
From | Date | Subject | |
---|---|---|---|
Next Message | Szabo Zoltan | 2001-09-07 10:22:45 | Re: problem with selects based on dates |
Previous Message | Joshua Drake | 2001-09-07 06:31:18 | Re: PHP performance problems with postgres |