From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, cnliou(at)eurosport(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: What Is The Firing Order? |
Date: | 2001-09-07 18:13:59 |
Message-ID: | 200109071813.f87IDxQ29420@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> The alphabetical ordering would change the order, but only with respect to
> the new constraint and existing ones not between the existing ones. The
> advantage here is that making a trigger fire before an existing one is
> easy, since you can name before it.
>
> The oid ordering has the property that the triggers would by default run
> in creation order. Creating a new trigger would always put it at the end
> unless you've wrapped oids which is nicer than having to worry about
> interactions between the new trigger and existing ones based on where it
> is (although you have to do that now), however putting a trigger before
> an existing one means dropping and recreating one or more of your existing
> triggers... all of the ones from where you want to put it in the order to
> the last one.
Good points. It is a tradeoff between making things stable for people
who don't notice the order vs. making it easy to define the ordering.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | mike | 2001-09-07 18:24:58 | Undefined All PQ keywords |
Previous Message | Stephan Szabo | 2001-09-07 18:12:21 | Re: What Is The Firing Order? |